It is already enabled.
Main Topics
Browse All Topics
Loading Advertisement...
Question
Visual Studio 2005 stops program instead of dedugging on error
My Visual Studio 2005 suddenly started ending program execution as if it hit an End statement when it encounters a run-time error of any kind. It used to start the debug. Any advice?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Subscribe now for full access to Experts Exchange and get
Instant Access to this Solution
- Plus...
- 30 Day FREE access, no risk, no obligation
- Collaborate with the world's top tech experts
- Unlimited access to our exclusive solution database
- Never be left without tech help again
Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.
- "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
- "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
- "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.
See what Experts Exchange can do for you.
Got a question?
We've got the answer.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
Need individual assistance?
Our experts are ready to help.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Want to learn from the best?
Read articles from industry experts.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Working on a long term project?
Store your work and research.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Trusted by the world's most respected brands.
Faithfully serving IT professionals since 1996.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Free Tech Articles
-
WARNING: 5 Reasons why you should NEVER fix a computer for free.
It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
-
SCCM OSD Basic troubleshooting
SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
-
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
-
Create a Win7 Gadget
This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
-
Outlook continually prompting for username and password
There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
-
Backup Exchange 2010 Information Store using Windows Backup
There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...
Cloud Class Webinars
- Avoiding Bugs in Microsoft Access
Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
- Top 10 Best New Features in Visio 2010
Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
- IT Consultant Business Secrets Revealed
Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
- Disaster Recovery and Business Continuity
Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
- Organize Your Visio Diagrams with Containers and Lists
Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
- How to Us Objects, Properties, Events and Methods in Microsoft Access
Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Answers
And have you implemented Try ... Catch block to get the error ?
Also try one thing:
Project menu > Properties > Application tab > View Application Events
Then:
Private Sub MyApplication_UnhandledExc
ByVal e As Microsoft.VisualBasic.Appl
Handles Me.UnhandledException
MsgBox(e.Exception.Message
End Sub
This is ANY litlle bug, not critical or where a user may have entered something wrong.
Right now I am chasing a bug that makes the program quit when you click on a certain tab in a form. Some textboxes have been renamed and changed. I am looking thru hundreds of lines to find exactly where the bug is. With the exception, it would have been fixed in under 30 sec.
Wierd. If I build it and run it outside VS, the UnhandledException sub works. It still does not tell me where it happened like VS did a week ago when making software was still profitabe for me....
I miss the happy VB6 days so much. Back when working after midnight menat to solving the customers problem rather than Microsofts.
>> Second try it also just threw me out of the program. No box at all.
The second you used in the exception ?
Catch ex As Exception
msgbox(Err.Number)
End Try
Just one more crazy thing! Can you create a new project and copy the files from that application to the right place (just forms, classes, modules, datasets). Then in the Menu project select "Show all files" and include then in your application.
I'm getting out of ideas! Is the application to big or can you upload it (database also) ? you can remove the unnecessary stuff.
Is this behaviour specific to this solution/project? Or if you create a completely new project, containing something very simple but including an error, do you get the same behaviour in that, too?
Try a new project, one form, one button, this code
Public Class Form1
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim a As Integer = 0
Dim b As Integer = 6
Dim c As Integer = b / a
End Sub
End Class
If that just ends, save the solution, go to the project folder, open the .vbproj file with NotePad and paste the contents back here. Then, rather than us guessing at settings etc, we will have a known output from your system to compare with what our systems produce for the same thing.
If that behaves properly (i.e. breaks at the offending line) then you can either post the contents of the .vbproj file for the "bad" project here, or yourself compare the settings as between the "good", new project file and the "bad", old one.
I am not sure about this, but my thinking is that - even if the problem arises from a general setting rather than a specific Application setting - it should be reflected somewhere in the file which controls the specific build/s.
Roger
There's a thread here which seems consider a whole range of possibilities which MIGHT be relevant here. Warning: it's long and (I found) a bit confusing. But it goes over so much ground that I imagine the answer for this case is probably in there somewhere.
http://forums.msdn.microso
Roger
I think it might be a good idea to post the .vbproj file contents. You could either do it from notepad with a copy and paste, or rename it to .txt, or zip it up. It's just that, so far as I know, the "Attach File" facility won't accept a .vbproj extension, and it shouldn't be large enough, on its own, to warrant uploading to http://www.ee-stuff.com
Roger
Thanks. Unfortunately, I can't see anything odd about that at all. It is, so far as I can see, identical in all "build-significant" respects (that is, leaving aside references to project-specific items, etc) to what works OK for me.
I think it unlikely, because even if this were the case I would not expect the application just to End, but have you checked that the Debug build configuration hasn't got set to Release by accident? You can check that either in the Configuration Manager or by opening the .sln file and looking under GlobalSection(ProjectConfi
Apart from that, I am out of ideas, I'm afraid. It does seem - from the link I posted earlier - that all sorts of unexpected factors can affect debugging behaviour. But as I have no personal practical experience of the problem, and I've exhausted my limited theoretical knoweldge on the topic, I'll have to leave it at that.
Good luck with it.
Roger
I read your question and recalled I had the same issue and I just learned to deal with it.
I got to investigating the first suggestion and knew I could really benefit from this "Exception assistant", and realized this feature only works for uncaught exceptions.
I was catching all exceptions and emailing an error, which is why I never saw it. Once I commented out the "Catch" part of my application, the exception assistant worked fine!
Perhaps this may be of use to you?
>> Wierd. If I build it and run it outside VS, the UnhandledException sub works.
FYI: This is a known issue. I *think* the decision was made to do this in order to make debugging uncaught exceptions easier while running from the IDE.
I see Roger has already made my suggestion -- it sounds like you're not running in debug mode. This would explain why you're not getting a decent stack trace for debugging -- you need the debug symbols to see line numbers rather than just method names of where the code failed.
I use the exception assistant to find out where I may have obvious errors before I even place try catch, so that is not the case. The last thing I want is to have the program ignore if I made a wrong object reference. Right now the program execution just stops as if you hit an end statement. That does not help me at all and now I can guessing where the error is. Before, VS came up and said "here"
you can try disabling the "just my code" in tools/options/debugging
if that does not work, you can try just-in-time debugging - also from tools/options/debugging/ju
hth,
A.
There must be a way to restore the regular an very useful exception handler in VS. I started moving all the files, classes etc. into a new project. What a disaster. I am still trying to even make the first form appear without useless error codes from VS.
I appreciate all the workarounds that you guys suggest. It almost appear normal that these things happen in VS and people are getting used to unexplainable Microsoft errors that people have to get creative to resolve.
Have you tried a new project, with no code and a simple like this (below) to see if the exception assistant pops up?
Throw New ApplicationException("blah
If it does, then you know it's a problem with your current project, code or setup. If it doesn't, then it's probably something to do with visual studio.
I have a June 20th deadline that is creeping up on me. I have almost messed with this for a week now and nothing. Is there anybody who know VS inside and out that would be willing to take a look at this thru phone and remote assist? Cash will be offered if the point are not enough. Yes, I am desperate.
This is the only project where this is happening. Starting a new project and throwing exceptions works fine.
As I already post it before:
"I'm getting out of ideas! Is the application to big or can you upload it (database also) ? you can remove the unnecessary stuff."
I'm shure that I or other expert will try to help you. As you know it's not easy to find a decente solution for this problems without the code.
I would venture to say at this point this question is going in circles because you are not responding to all experts that are trying to help you. I for one have proposed (in my opinion) two good concepts when dealing with the exception assistant, and you have not once responded specifically to my suggestion, leading me to believe you either didn't read it or you never tried it out?
raterus: If you look further back you will see that a new project does not create the same problem. Read >> This is the only project where this is happening. Starting a new project and throwing exceptions works fine. << from earlier reply.
I use the exception as a part of my work to develop and debug. I guess that is one handicap when you come from VB6. Besides that, the Unhandledexceptions sub for the application does not work either.
What if on the first line of Form_Load in your main form, you put a statement like
Throw New ApplicationException("blah
Do you see the exception assistant? If not, you should be able to set a breakpoint on this statement, step into the procedure and at least debug to figure out what code is catching your exceptions?
'CDTsoftware.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_M
'CDTsoftware.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_3
'CDTsoftware.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_3
'CDTsoftware.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_3
Is 'Just My Code' supposed to be enabled?
Try Catch works fine!
It is when I don't use it and rely on the one that VS should send back. As mentioned some posting ago, I normally write the code and then use the exception handler to find where the try catch go because tthe program is unable to handle the unexpected conditions.
Yes, that was where the breakpoint was.
did you try the 'exceptions' dialog - enabling all on thrown column? i realy beleive that it's not stopping into the debugger because you have some try-catch and the exception is handled somewhere. if you enable the exceptions from the exception dialog, it should stop even if the exception it's handled.
if the code does not crash in your code, the you have to disable just my code.
hth,
A.
Here is a status on the situation for those who are interested. Microsoft is really scratching their heads on this one. The program has two database connections, one OleDB and a SQLclient for a remote server. Both of them work fine, but once you have had the SQL connection open, it kills the debugger in VS. Even if you close and dispose. Remove the .open statement and everything works fine in the entire application. MS is now analyzing a memory dump to see why.
Any comments?
Problem solved. A process called bmnet.dll (Byte mobile dll that comes with AT&T Blackberry communication mgr) started taking over the exception handling as soon as the program tried to use the sockets. That happened when the program opened the remote SQL Server connection. After that, it would handle all exceptions from there on regardless of the type. It actually just ignored the exception and caused VS to just stop. I removed the AT&T Com. mgr. and everything works fine. Who would have guessed that?
3 Ways to Join
Business Accounts
- Perfect for organizations
- Multiple users
- Save over 36%
- Create a Business Account
Answer for Membership
- Earn free access
- Showcase your knowledge
- No credit card required
- Sign Up to Answer
Loading Advertisement...
by: jpaulinoPosted on 2008-05-30 at 05:11:58ID: 21676959
Go to Tools - Options - Show All Settings - Debugging - General and then check the Enable The Exception Assistant