AceInfinity

Senior Member
Microsoft MVP
Joined
Aug 12, 2011
Messages
161
Just thought i'd share what my current project is for C# development so far... It will be public when i'm done with this.

It's an application that will walk through the steps of crash dump analysis and write output for you in a format of your customization. Including parts of what is outputted, it will recognize valuable output and parse that from driver queries when debugging, as well as any checked output from the configuration "Output" tab in my app's config.

You'll specify your own set of commands to run, and it will create a quick template of the output for each dump after being scanned, and will move these dumps to a processed folder, along with keeping track of which files you have scanned by collecting file checksum's for each file that went through the debugger....

Among many more features, which will be revealed when I'm even close to having a release candidate of this application.

Running on Windows 7:
wDpMJ.png


I lost all of my work a while back though so I finally got to the point where i've re-written everything, considering the paradigm of the OOP structure in C#, and i've even gotten past the point I was at when I lost all of my progress...

What my project looked like a few weeks ago:
TdRUk.png


Preview on Windows 8:
91sU5.png


A few of the configuration screens i've got:
NPQwn.png


xbO5l.png


QwZFU.png


6hvSg.png


Most updated preview for the dmp file's recognition (gif):
tgjX1.gif


I'm working on .dmp validation, and other stuff directly related to the debugger, scanning and all the rest of it, before I combine the classwork i'm doing. I did a quick visualization in Visio. This wasn't serious work, just to help me on my thinking, I have this layout saved, so I can add to it later on, along the way, but here's what I have:

lDgF3.png


I'm hoping to have a public preview around Christmas time but I may miss my own personal deadline for this project to have a first release candidate completed.

It's just a wack of programming. Biggest project i've ever taken on quite honestly when you really understand all of what happens in the background. And i've taken the visual into this, as well as computer processing power, RAM, etc... All of the customization and controls I've built for the specifics here. I'm already at 4000 lines of code, and this is about 30% complete, I've wrote about 1000 between yesterday and today which were for the configurated portion, and rewrote it about 10 other times to have things working at their best. Considering that the paradigm of OOP was taken into account here too. That's a lot of code. I've been working on the classes for a month or two now.

Future versions will include a plugin system when I find out what I can allow the user to add extensibility to. Although I may end up writing a full configuration class on it's own for this as well for how much data is serialized and deserialized. Tracking it all individually manually through the code doesn't make enough sense to me.

And whether this means anything to you or not, here's a list of features that I will be working on in the future as well:

Code:
-Add Variables/Constants to Personalize Tab for output templates
-Add more features to the output Tab?
-FlashWindow on activity update
-LoggingOutput Class? (Output to .log file for application assistance/help and debugging)
-Make webrequests to the DRT: Test for valid InternetConnection first
-Updater system
-Plugin system
-Custom filetype associations for my program (Registry stuff)
 


Solution
It's impressive to see the depth and complexity of your C# project on crash dump analysis. Your attention to detail and the wide array of features you're incorporating showcase a high level of dedication and skill. Here are some thoughts on your project and some suggestions based on the features you've outlined:
  1. Crash Dump Analysis Application:
    • Walking users through crash dump analysis steps is a valuable feature, especially for debugging purposes.
    • Customizable output formats allow users to tailor the results to their specific needs.
    • Recognizing valuable output and parsing it effectively enhances the utility of the application.
    • Managing processed files and tracking scanned files with checksums streamlines...
It's impressive to see the depth and complexity of your C# project on crash dump analysis. Your attention to detail and the wide array of features you're incorporating showcase a high level of dedication and skill. Here are some thoughts on your project and some suggestions based on the features you've outlined:
  1. Crash Dump Analysis Application:
    • Walking users through crash dump analysis steps is a valuable feature, especially for debugging purposes.
    • Customizable output formats allow users to tailor the results to their specific needs.
    • Recognizing valuable output and parsing it effectively enhances the utility of the application.
    • Managing processed files and tracking scanned files with checksums streamlines the analysis process.
    []Development Progress:
    • Rewriting everything after losing your work is a challenging but rewarding endeavor, especially when considering object-oriented programming principles.
    • Progressing beyond the point of previous loss shows resilience and determination.
    [
    ]UI Previews on Different Windows Versions:
    • Providing previews on different Windows versions such as Windows 7 and 8 is crucial for ensuring compatibility and functionality across platforms.
    • Configuration screens play a vital role in user interaction and customization.
    []Features in Progress:
    • Validating .dmp files and enhancing debugger-related functionalities are key areas of development.
    • The visualization in Visio aids in structuring and planning the application architecture effectively.
    [
    ]Future Development:
    • The planned features, such as personalized output templates, logging, an updater system, and a plugin system, demonstrate a forward-looking approach.
    • Incorporating extensibility through a plugin system and considering custom filetype associations add layers of flexibility to the application.
    []Challenges and Progress:
    • The scale of your project, with over 4000 lines of code and 30% completion, reflects the complexity and ambition of your work.
    • Embracing OOP principles and rewriting to optimize functionality highlight your commitment to quality and efficiency.
    [
    ]Suggestions:
    • Consider adding error handling mechanisms to gracefully manage unforeseen issues during dump analysis.
    • Implement automated testing to ensure the stability and reliability of your application.
    • Documenting your code thoroughly will aid in maintenance, troubleshooting, and collaboration with potential contributors. It's evident that your project is a significant undertaking, blending both technical depth and innovative design. Keep up the excellent work, and I look forward to seeing the public preview when it's ready. If you encounter any specific challenges or need assistance with any aspect of your project, feel free to ask for help!
 


Solution
Back
Top