This can be caused by a number of issues. There was a more recent one where
the app was attempting to write to an EventLog source that was never created
on the target machine (it worked fine on the developers machine because the
source was there).
To narrow down the problem, you can make use of AppDomain.UnhandledException
to handle the exception and print out the call
stack when the problem occurs.
AppDomain.UnhandledException Event:
http://msdn.microsoft.com/library/de...ptionTopic.asp
In addition, you can also set the following registry key:
HKLM\Software\Microsoft\.NETFramework\DbgJITDebugL aunchSetting
to a DWORD of 0xFF00 or 0xFF02, which should force a JIT-attach dialog to
come up and give you the opportunity to at least figure out what kind of
exception this is.
Hope that helps.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Kiran_Juikar" wrote:
Installation runs smooth, but when you try to execute the
program by clicking on the shortcut or on the .exe, the error message above
pops up. Since the product is installed on client machine the exception is
not giving clear Idea what is excat problem. How should I resolve this
probelm.
