.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Home >> Articles >> Bugs & Resolutions >> Post New Resource Bookmark and Share

 Subscribe to Articles

Hide unhandled exception dialog

Posted By :Pankaj Mishra      Posted Date :26/06/2009   Points :25   Category: Bugs & Resolutions    URL: http://www.dotnetspark.com
    


Hide unhandled exception dialog.

Sometimes we see unhandled exception dialog box with comment "unhandled exception has occurred in your application" with three options Details, Continue and Quit options  in .NET application when use threading, or uses com component in our applciation. If you click on Continue the application will ignore the error and run smoothly.


So whats the solution?

Well the best way to figure out what causes the unhandled exception and try to resolve it.
But there is other way to hide unhandled dialog box using registry settings.

Manually you can change the registry and the registry path is


HKEY_LOCAL_MACHINE /SOFTWARE/MICROSOFT/.NETFramework/


"DbgJITDebugLaunchSetting" and set it value to 1 (By default it will be 16)
Once you set the value to 1 you will not able to see the unhandled dialog box again

If you want to set this value programmatically here is the code

C# Example

string registry_path = @"Software\Microsoft\.NETFramework\";
using (RegistryKey regKey = Registry.LocalMachine.OpenSubKey(registry_path, true))
if (regKey != null)
"DbgJITDebugLaunchSetting", 1);

VB.Net Code Sample

Dim registry_path As String = "Software\Microsoft\.NETFramework\"

Using regKey As RegistryKey = Registry.LocalMachine.OpenSubKey(registry_path, True)   
If regKey IsNot Nothing Then
        regKey.SetValue("DbgJITDebugLaunchSetting", 1)
    End If
End Using

Hope this will help all who wants to hide Hide unhandled exception dialog

Cheers
Pankaj


Featured Articles


Best Practices No 5: - Detecting .NET application memory leaks
Memory leaks in .NET application have always being programmer's nightmare. Memory leaks are biggest problems when it comes to production servers. Productions servers normally need to run with least down time. Memory leaks grow slowly and after sometime they bring down the server by consuming huge chunks of memory. Maximum time people reboot the system, make it work temporarily and send a sorry note to the customer for the downtime. ... Read More
.NET Best Practice No: 1:- Detecting High Memory consuming functions in .NET code
One of the important factors for performance degradation in .NET code is memory consumption. Many developers just concentrate on execution time to determine performance bottle necks in a .NET application. Only measuring execution time does not clearly give idea of where the performance issue resides. Ok, said and done one of the biggest task is to understand which function, assembly or class has consumed how much memory. In this tutorial we will see how we can find which functions consume how much memory. This article discusses the best practices involved using CLR profiler for studying memory allocation.... Read More
How to improve your LINQ query performance by 5 X times ?
LINQ has been criticized by many early adopters for its performance issues. Well if you are just going to drag and drop using DBML code generator I am sure you will land up in to mess. Try doing this make a simple LINQ to SQL project using DBML and see your SQL profiler, I am sure you will never like to touch DBML code generator again. ... Read More
Responses

No response found. Be the first to respond this post

Post Comment
You must Sign In To post reply

    Related Resource From The Same Category

Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend