It does stop at Debugger.Break()..which is a step forward?
This the text i always get..i know what it is saying but no idea how to fix
it....
Locating source for
'Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs'. Checksum: MD5 {6a
78 31 4f a7 90 9 5 a4 60 57 e5 da a7 fb f3}
Determining whether the checksum matches for the following locations:
1: Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs Checksum: MD5 {5
b7 15 40 ac be b0 68 0 7 4 5b 27 df 7d 97} Checksum doesn't match.
The file 'Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs' exists.
Looking in script documents for
'Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs'...
Determining whether the checksum matches for the following locations:
1: Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs Checksum: MD5 {5
b7 15 40 ac be b0 68 0 7 4 5b 27 df 7d 97} Checksum doesn't match.
Looking in the projects for
'Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs'.
The file was not found in a project.
Looking in directory 'q:\'...
The debug source files settings for the active solution indicate that the
debugger will not ask the user to find the file:
Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs.
The debugger could not locate the source file
'Q:\Data\Clients\gime\PoppClientDotNet2\Popp\MainForm.cs'.
From: [email protected] [mailto:[email protected]]
On Behalf Of Corneliu I. Tusnea
Sent: Wednesday, 8 December 2010 4:18 PM
To: ozDotNet
Subject: Re: The breakpoint will not currently be hit..nightmare!
Try to add in your code a Debugger.Break() see what's happening.
On Wed, Dec 8, 2010 at 9:48 AM, Conrad Lang <[email protected]> wrote:
Have you checked the following:
1. All folders related to your projects in the "Temporary ASP.NET
Files" of all the "C:\Windows\Microsoft.NET\Framework\v?.?..." have been
deleted.
2. All bin and obj folders have been deleted (I know you've done this
already though but may as well clean again).
3. Check your projects are targetting the same .NET framework in the
project properties.
4. If you're debugging using IIS, check that the IIS AppPool is using
the same framework as your project properties.
5. Your solution startup projects are set to "multiple".
1. Your web services should be "run" (not "run without debugging").
2. Your client application or ASP.NET UI project should be "run" (not
"run without debugging").
6. Your breakpoints should be enabled (it's a silly suggestion but
sometimes I forget I disabled a breakpoint).
1. It might be worthwhile removing and adding the breakpoint again in
case the VS upgrade somehow mangled its references (it's a long shot but
worth a try?)
7. If you're using the built-in ASP.NET development web server, maybe
try change the port your dev ASP.NET app is running on.
Good luck,
Conrad.
On Wed, Dec 8, 2010 at 4:27 AM, David Kean <[email protected]> wrote:
Then this means that it is likely that sources/PDBs don't match what you are
debugging. Try deleting all obj/bin directories and do a rebuild.
From: [email protected] [mailto:[email protected]]
On Behalf Of Anthony
Sent: Tuesday, December 07, 2010 1:42 AM
To: 'ozDotNet'
Subject: RE: The breakpoint will not currently be hit..nightmare!
Not a solid circle..red border
From: [email protected] [mailto:[email protected]]
On Behalf Of David Kean
Sent: Tuesday, 7 December 2010 6:26 PM
To: ozDotNet
Subject: RE: The breakpoint will not currently be hit..nightmare!
Is the breakpoint a solid red circle once you've started debugging?
From: [email protected] [mailto:[email protected]]
On Behalf Of Anthony
Sent: Monday, December 06, 2010 8:06 PM
To: 'ozDotNet'
Subject: The breakpoint will not currently be hit..nightmare!
Upgraded my asp.net projects to VS2010 and now i can't debug my project as
the breakpoints are not being hit.
. I have deleted framework temporary files.
. Delete bin and obj directories.
. Re-referenced projects
. According the modules window..the symbols are being loaded.
....still no luck
Anyone have suggestion....i'm going crazy!!!!
Anthony
--
Regards,
Conrad Lang
Mobile: 04 2260 9718 | Home: 03 9029 2247
