Control throws error when compiled in release mode. but works nicely when compiled in debug mode.

Jigar Desai

This will sound weird but its happening Control throws error when compiled in release mode. but works nicely when compiled in debug mode. I have created class library which has several user controls, now one of the control is throwing null reference error.(object reference not set to instance of object). To trap exact place of error I recompiled this dll with debug option . to my surprise control works with out error when I compile with debug option. I tried switching .net frame work version 1.0 & 1.1 same thing happens with both. How I can trap error if I can not get error in debug mode? and what could be reason for this behavior

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Jigar Desai22y ago
As there was no error in debug mode i have to resort to following trick Divided method call which was throwing error in to some logical parts ,added code to add message(part xx executed) to Session object(HttpContext.Current.Session) in each section and then created page to grab that message. This gave me section which was throwing error then i repeted same step to zero out on line which was throwing error. For those who are wondering what are "Release-mode only bugs" this web log will explain. http://weblogs.asp.net/savanness/archive/2003/05/23/7496.aspx
+1
Jigar Desai22y ago
Have u add all the references of the class library/ Component you have created. I do not think my code would work even in debug mode with out correct references to required library, and error I am getting is null refrence error very different from one when you miss assembly references.
+1
Tanvir Huda22y ago
I am not sure where is the problem. But just a suggestion. Have u add all the references of the class library/ Component you have created. If u are using any special class library like activeX controls make sure u add them as a reference. Good luck
+1

Control throws error when compiled in release mode. but works nicely when compiled in debug mode.

Jigar Desai

22y14.2kVisual Basic .NET

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Jigar Desai22y ago
As there was no error in debug mode i have to resort to following trick Divided method call which was throwing error in to some logical parts ,added code to add message(part xx executed) to Session object(HttpContext.Current.Session) in each section and then created page to grab that message. This gave me section which was throwing error then i repeted same step to zero out on line which was throwing error. For those who are wondering what are "Release-mode only bugs" this web log will explain. http://weblogs.asp.net/savanness/archive/2003/05/23/7496.aspx
+1
Jigar Desai22y ago
Have u add all the references of the class library/ Component you have created. I do not think my code would work even in debug mode with out correct references to required library, and error I am getting is null refrence error very different from one when you miss assembly references.
+1
Tanvir Huda22y ago
I am not sure where is the problem. But just a suggestion. Have u add all the references of the class library/ Component you have created. If u are using any special class library like activeX controls make sure u add them as a reference. Good luck
+1