Deploy - Setup problem!! Installed program wont run!

[Eri523]

Fine you fixed it!

kernelbase.dll is mentioned in the error reports because that's where the original exception got thrown. If it wouldn't have been found, the message would have been considerale different (but I doubt that in this case the respective Windows installation would have properly started up in the first place).

The reason that the exception originates in the depths of a low-level system DLL most probably is at least part of the reason why the error information you got actually was rather sparse. When I get such reports about an exception thrown in my own code or in .NET framework code that has been called by mine, the stack trace usually isn't empty and is of great help in spotting the culprit function. (In a debug build the stack trace even refers to line numbers, but debug builds only run on systems with VS installed, and as I interpret your description, you probably would never have been able to reproduce the failure on such a system.)

One of the drastic bugs I spotted using the event log was caused by the subtle difference that under Windows 7 (and perhaps already Vista), the Form::Resize event gets fired indirectly from inside InitializeComponent() during form class contruction, but not under XP, which I have on my development machine. I can't remember ever haveing seen that documented anywhere. And my handler for that event wasn't prepared for being called with the class being initialized incompletely and hit a NullReferenceException when that happened.

All that pretty much demonstrates why it's important to test your code on others than the development machine too.

So, now may be a good occasion to mark the thread [RESOLVED].