By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,668 Members | 1,704 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,668 IT Pros & Developers. It's quick & easy.

Code failing silently

P: n/a
I seem to have acquired a strange issue here, some of my programs are
now failing silently, resuming without notification that anything went
wrong, both on my development machine and (I think) on the users
machines. For instance, I was just noticing a spot where a table
adapter's fill method fails, and the new form just opens up anyway
after skipping the rest of the form's Load procedure without any
indication anything went wrong. I haven't fiddled with any of the
debug settings, and I don't remember if this started when I upgraded
to VS 2008 or a while later. I am pretty sure it never happened in
2005 though.

What settings should I check or change to *make* it tell me something
went wrong? Sorry, I know this makes me seem like a lame developer,
it's just that the default debug settings have always worked fine for
me so I don't know much about altering them.

Bob Graham
Jul 3 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
sounds like you have a try/catch somewhere that is throwing the exception
away
"RvGrah" <rv****************@sbcglobal.netwrote in message
news:c4**********************************@u6g2000p rc.googlegroups.com...
>I seem to have acquired a strange issue here, some of my programs are
now failing silently, resuming without notification that anything went
wrong, both on my development machine and (I think) on the users
machines. For instance, I was just noticing a spot where a table
adapter's fill method fails, and the new form just opens up anyway
after skipping the rest of the form's Load procedure without any
indication anything went wrong. I haven't fiddled with any of the
debug settings, and I don't remember if this started when I upgraded
to VS 2008 or a while later. I am pretty sure it never happened in
2005 though.

What settings should I check or change to *make* it tell me something
went wrong? Sorry, I know this makes me seem like a lame developer,
it's just that the default debug settings have always worked fine for
me so I don't know much about altering them.

Bob Graham

Jul 3 '08 #2

P: n/a
gerry wrote:
sounds like you have a try/catch somewhere that is throwing the exception
away
- or a BackgroundWorker who silently "eats" the exception.

--
Michael Justin
SCJP, SCJA
betasoft - Software for Delphi™ and for the Java™ platform
http://www.mikejustin.com - http://www.betabeans.de
Jul 3 '08 #3

P: n/a
Thx for the input, but these ideas I've already looked at..

For instance, I'm getting this error:

A first chance exception of type 'System.NullReferenceException'
occurred in GranPoSys.exe

From this code line:

ultraGridPrintDocument1.Grid.DisplayLayout.Appeara nce.BorderColor =
Color.White;

because the "grid" property of the ultraGridPrintDocument had not been
set. But, instead of breaking into the running code, the user
interface just pops back up ready to interact with as though nothing
had gone wrong. The rest of the procedure does not complete though. I
know that with "Just My Code" enabled, it wouldn't break into the
third party control code, but in this case the error *is* happening at
"my code" level. It always used to break in but now it no longer does.

I've looked into the Exceptions list under the debug menu and it is
set to break when a user-unhandled null reference excetion happens.

Bob

On Jul 3, 10:29*am, RvGrah <rvgrahamsevaten...@sbcglobal.netwrote:
I seem to have acquired a strange issue here, some of my programs are
now failing silently, resuming without notification that anything went
wrong, both on my development machine and (I think) on the users
machines. For instance, I was just noticing a spot where a table
adapter's fill method fails, and the new form just opens up anyway
after skipping the rest of the form's Load procedure without any
indication anything went wrong. I haven't fiddled with any of the
debug settings, and I don't remember if this started when I upgraded
to VS 2008 or a while later. I am pretty sure it never happened in
2005 though.

What settings should I check or change to *make* it tell me something
went wrong? Sorry, I know this makes me seem like a lame developer,
it's just that the default debug settings have always worked fine for
me so I don't know much about altering them.

Bob Graham
Jul 12 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.