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

.NET Breakpoint execution failure

P: n/a
I have been working on a ASP.NET project with VB Code
behind for a while
now, and it ran perfectly up until now. When I try to set
a breakpoint or a
watch at certain parts of the project, even though that
code executes, no
break is made. I validated that it was making it up and
after the
breakpoint, but still no breakpoint execution or ability
to create a watch.
I am using VS.NET 2003 on a Windows 2003 Server.

Steps I have completed to try and resolve:
- Made sure all debug flags are set (not set to release)
(fails)
- Created a new project and migrated code over to it
(fails)
- Created a new project and entered a breakpoint for a
response.write
call (fails)
- Rebuilt the solution multiple times (fails)
- Set startup page and selected Debug>Start (fails)
- Validated that my web.configs has <compilation
defaultLanguage="vb"
debug="true" /> (fails)
- ASP.Net Debugging selected from Configuration
Properties>Debugging
(fails)
- Deleted the .dll and .pdb files under the project/Bin
directory and
rebuilt (fails)

The only way to get a breakpoint is to
enter "System.Diagnostics.Debugger.Break()".

TIA

John

Nov 20 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Can you use any of the Debug Methods like Debug.Assert? A coworker of mine
had the same behavior and it was really weird. It started when he installed
2003. We Undefined then redefinged the debug constants, then wrote in some
Debug.Assert logic and things started to work after that. I have no idea
why and it could just have been coincidence. However, we have all had some
weird debugging behavior, particularly with ASP.NET.
"John Kutsor" <jo*********@us.army.mil> wrote in message
news:02****************************@phx.gbl...
I have been working on a ASP.NET project with VB Code
behind for a while
now, and it ran perfectly up until now. When I try to set
a breakpoint or a
watch at certain parts of the project, even though that
code executes, no
break is made. I validated that it was making it up and
after the
breakpoint, but still no breakpoint execution or ability
to create a watch.
I am using VS.NET 2003 on a Windows 2003 Server.

Steps I have completed to try and resolve:
- Made sure all debug flags are set (not set to release)
(fails)
- Created a new project and migrated code over to it
(fails)
- Created a new project and entered a breakpoint for a
response.write
call (fails)
- Rebuilt the solution multiple times (fails)
- Set startup page and selected Debug>Start (fails)
- Validated that my web.configs has <compilation
defaultLanguage="vb"
debug="true" /> (fails)
- ASP.Net Debugging selected from Configuration
Properties>Debugging
(fails)
- Deleted the .dll and .pdb files under the project/Bin
directory and
rebuilt (fails)

The only way to get a breakpoint is to
enter "System.Diagnostics.Debugger.Break()".

TIA

John

Nov 20 '05 #2

P: n/a
How would i implement the debug.assert in my code?
Page_init?

john
-----Original Message-----
Can you use any of the Debug Methods like Debug.Assert? A coworker of minehad the same behavior and it was really weird. It started when he installed2003. We Undefined then redefinged the debug constants, then wrote in someDebug.Assert logic and things started to work after that. I have no ideawhy and it could just have been coincidence. However, we have all had someweird debugging behavior, particularly with ASP.NET.
"John Kutsor" <jo*********@us.army.mil> wrote in message
news:02****************************@phx.gbl...
I have been working on a ASP.NET project with VB Code
behind for a while
now, and it ran perfectly up until now. When I try to set a breakpoint or a
watch at certain parts of the project, even though that
code executes, no
break is made. I validated that it was making it up and
after the
breakpoint, but still no breakpoint execution or ability
to create a watch.
I am using VS.NET 2003 on a Windows 2003 Server.

Steps I have completed to try and resolve:
- Made sure all debug flags are set (not set to release)
(fails)
- Created a new project and migrated code over to it
(fails)
- Created a new project and entered a breakpoint for a
response.write
call (fails)
- Rebuilt the solution multiple times (fails)
- Set startup page and selected Debug>Start (fails)
- Validated that my web.configs has <compilation
defaultLanguage="vb"
debug="true" /> (fails)
- ASP.Net Debugging selected from Configuration
Properties>Debugging
(fails)
- Deleted the .dll and .pdb files under the project/Bin
directory and
rebuilt (fails)

The only way to get a breakpoint is to
enter "System.Diagnostics.Debugger.Break()".

TIA

John

.

Nov 20 '05 #3

P: n/a
Nevermind,
I have implemented debug.assert, which works fine.
So why does the breakpoints and watches just all the
sudden stop working?
If you come across the solution let me know!

thanks,
John
-----Original Message-----
Can you use any of the Debug Methods like Debug.Assert? A coworker of minehad the same behavior and it was really weird. It started when he installed2003. We Undefined then redefinged the debug constants, then wrote in someDebug.Assert logic and things started to work after that. I have no ideawhy and it could just have been coincidence. However, we have all had someweird debugging behavior, particularly with ASP.NET.
"John Kutsor" <jo*********@us.army.mil> wrote in message
news:02****************************@phx.gbl...
I have been working on a ASP.NET project with VB Code
behind for a while
now, and it ran perfectly up until now. When I try to set a breakpoint or a
watch at certain parts of the project, even though that
code executes, no
break is made. I validated that it was making it up and
after the
breakpoint, but still no breakpoint execution or ability
to create a watch.
I am using VS.NET 2003 on a Windows 2003 Server.

Steps I have completed to try and resolve:
- Made sure all debug flags are set (not set to release)
(fails)
- Created a new project and migrated code over to it
(fails)
- Created a new project and entered a breakpoint for a
response.write
call (fails)
- Rebuilt the solution multiple times (fails)
- Set startup page and selected Debug>Start (fails)
- Validated that my web.configs has <compilation
defaultLanguage="vb"
debug="true" /> (fails)
- ASP.Net Debugging selected from Configuration
Properties>Debugging
(fails)
- Deleted the .dll and .pdb files under the project/Bin
directory and
rebuilt (fails)

The only way to get a breakpoint is to
enter "System.Diagnostics.Debugger.Break()".

TIA

John

.

Nov 20 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.