Hi Les,
Can you tell me the type of your .Net application, is it console, Winform?
Normally, the verbose error dialog will only show in the .Net Winform
application. .Net console application will not show verbose error dialog.
Please refer to the link below to understand the default behavior of
unhandled error in different type of .Net applications:
http://msdn.microsoft.com/msdnmag/is...T/default.aspx
However, in .Net Winform, if the .Net unhandled exception is generated
before Application.Run() method is called, the verbose error dialog will
not show, the behavior will be same as console application, which pops a
'has encounted a problem' dialog in a clear machine. Also, if the exception
is generated in a non-GUI worker thread, it will behave like console
application.
You may register AppDomain.UnhandledException event yourself to be notified
the error in the current AppDomain. In this event, you may use
Environment.StackTrace to examine the stace trace of this unhandled
exception. This will help you to examine the cause of this problem.
If you want to perform an intensive debugging for this problem in the
client machine, I would recommend you to installed a light-weight windbg on
the client machine to catch this unhandled exception, see my blog entry
below for the configuration and details:
"How to debug application crash/hang in production environment?"
http://blogs.msdn.com/msdnts/archive...pplication-cra
sh-hang-in-production-environment.aspx
Additionally, based on your last reply, it seems that your problem is
caused by .Net Code Access Security check. You may run "caspol.exe -s off"
in "Visual Studio 2005 Command Prompt" to turn off the .Net2.0 CAS check
temparily. If this error goes away, it means that it is caused by CAS
check. If you have determined that the problem is caused by CAS, you may
follow the following steps to evaluate the permission set and code group of
your application assembly:
You can open ".Net Configuration 2.0" tool from "Administrative tools" in
Control Panel. Click "Runtime Security Policy" node the left panel. Then
click "Evaluate Assembly" link in the right panel.
In the popup dialog, input your assembly path, and click next to evaluate
your assembly permission set. Normally, it should be Unrestricted.
Please paste any details here for further analysis, thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.