Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / December 2005

Tip: Looking for answers? Try searching our database.

VS.NET 2003, often won't stop at breakpoints, at wits end!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Matt Greer - 14 Dec 2005 15:38 GMT
Hello,

I post this message in desperation. Not stopping at breakpoints while
debugging is a very common problem with my use of VS.NET 2003 and I'm
hoping someone can shed some light.

I am using:
-- Visual Studio.NET 2003 version 7.1.3088
-- Windows XP Pro, with Service Pack 2, version 5.12600  build 2600
-- Coding in C#

I am already sure that:
-- I am running in Debug mode
-- Generation Debugging Information is true for all projects
-- the DEBUG preprocessor constant is defined
-- The breakpoint is enabled
-- The breakpoint should be traversed (ie that section of code really
is executed)
-- the pdb file for the assembly is present in the same directory as
the assembly and exactly corresponds to that version of the assembly.
-- The Modules window shows the assembly is loaded and with symbols.

Also:
-- I have cleared the VS cache under <username>/local
settings/application data/assembly
-- I've completely wiped my local copy of the project and re-obtained
it from source control
-- and even more, this computer was recently formatted and reinstalled
with a fresh copy of Windows and VS.NET

And finally :) :
-- It appears to be totally random. My solution contains a mixture of
native and .NET projects. I can get it to stop at breakpoints in
certain projects just fine. If I attempt to start debugging from a
project that is wokring ok and attempt to step into the problem
project, I get a "No source code is available at this location" error.
-- Coworkers working on the same project have no problem debugging on
their machines.

I have this problem all the time. And the solution almost always seems
to be completely random. Sometimes rebooting my machine does it.
Sometimes relaunching VS. Sometimes switching over to release and back
to debug mode. But no solution ever seems to work reliably. It's
driving me crazy and really making me wish I had a job coding in Java
:)

Thanks for any ideas,
Matt
Kevin Spencer - 14 Dec 2005 15:57 GMT
Right-click the Solution, go to Configuration Manager, and see whether all
projects are set to build as Debug.

Signature

HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

> Hello,
>
[quoted text clipped - 44 lines]
> Thanks for any ideas,
> Matt
Pavel A. - 15 Dec 2005 11:19 GMT
Hi,
We've seen same problem recently with native c++ program.
Do you have any other debug/profile tools installed, like Compuware
devpartner?

--PA

> Hello,
>
[quoted text clipped - 44 lines]
> Thanks for any ideas,
> Matt

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.