Well, you could have a VBS script handed out with installation instructions I suppose for both adding and removing the native image from the cache for any user using your application (label the step as optional I guess). They would otherwise need to know how to use NGEN. I have the Ultimate version of Visual Studio, before 2010, but now i'm using 2012. I have not checked, but perhaps there would be a dll out there which would be the wrapper for NGEN kind of like PEVerify? I'd be curious myself to see what there is for NGEN.
I was just asking about the try statements though, mostly because of a couple things, specified below:
- Your debugging time for finding bugs to the app is going to be significantly more difficult, and more of a hairpulling event, than a fixing event. Errors are great to look at, and you're probably getting nothing where you should be seeing certain errors in order to try and fix the issue at it's base. This reduces the efficiency of your debugging as well for that reason.
- It will significantly reduce the performance of your apps if you're not dealing with exceptions properly. Having exceptions thrown and ignored at runtime enough times will negatively impact the overall experience the end-user has with your app, comparative to if you were to check for the exceptions yourself instead of allowing the exceptions to decide what your app does next.
I was fooling around with various .NET utilities, and tried to decompile your app back to MSIL, which works, but not sure if the conversion from VC++ over to C#, VB.NET would have added those, MSIL would be most accurate anyways... Would have caused those changes. I'm seeing lots of indentations after indentations of try statements lol. I only checked DmpList though.
