Debugging Broken

  • Thread starter Thread starter Hillbilly
  • Start date Start date
H

Hillbilly

I lost the ability to debug websites something about no symbols. Any tips on
putting symbols on the machine and configuring VS2008 so I can debug
websites?
 
Hillbilly said:
I lost the ability to debug websites something about no symbols. Any
tips on putting symbols on the machine and configuring VS2008 so I can
debug websites?
Click to expand...

That usually means that VS and the IIS Web application code no longer
has a valid connection for the Web application, like you told IE to work
off line and never told IE to come on line again will produce the
situation you're talking about.
 
There are a couple of reasons this happens. One annoying reason is the
ASP.NET Temp files are munged up. This is especially true with AJAX and
other new bits, but I have seen it in non-new sites, esp. when using Profile
with extra elements. To solve this, go to
c:\windows\microsoft.net\framework\{version #]\ASP.NET Temporary files and
clear everything out. You may have to restart IIS to get this working.

The FAQ has a couple of additional hints, although I am not sure they will
solve anything directly:
http://blogs.msdn.com/jimgries/pages/visual-studio-debugger-faq.aspx

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Blog:
http://feeds.feedburner.com/GregoryBeamer

*********************************************
| Think outside the box |
*********************************************
 
ThankU I think that's it as I had in fact deleted some temp directories in
that path and it seems some of the temp files are no longer in synch with
other temp directories. I'll go whack everything under the parent and see
how it goes.

Cowboy (Gregory A. Beamer) said:
There are a couple of reasons this happens. One annoying reason is the
ASP.NET Temp files are munged up. This is especially true with AJAX and
other new bits, but I have seen it in non-new sites, esp. when using
Profile with extra elements. To solve this, go to
c:\windows\microsoft.net\framework\{version #]\ASP.NET Temporary files and
clear everything out. You may have to restart IIS to get this working.

The FAQ has a couple of additional hints, although I am not sure they will
solve anything directly:
http://blogs.msdn.com/jimgries/pages/visual-studio-debugger-faq.aspx

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Blog:
http://feeds.feedburner.com/GregoryBeamer

*********************************************
| Think outside the box |
*********************************************
Hillbilly said:
I lost the ability to debug websites something about no symbols. Any tips
on putting symbols on the machine and configuring VS2008 so I can debug
websites?
Click to expand...
Click to expand...
 
ThankU. That's an interesting hypothesis. I think Cowboy's reminder is going
to work it out this time as I note in my reply. I have never taken IE
offline. What for? :-)
 
Hillbilly said:
ThankU. That's an interesting hypothesis. I think Cowboy's reminder is
going to work it out this time as I note in my reply. I have never taken
IE offline. What for? :-)
Click to expand...

Well, if you're doing more than one task, like surfing on a dial-up
somewhere, you're doing ASP.Net development too, have to get off the
phone line, pull the phone line out the jack, IE asked do you won't to
work off-line or connect back using the phone line, and you select
work-off line, then you will get that condition of Debug and the symbols
are lost.

As a matter of fact, the ASP.Net application and IIS went on the blink
too on the laptop with me cussing it all out, before I stumbled upon let
me connect on the dial-up and make IE go back online.

And believe me I stumble into the solution. :)
 
I see, thanks for bringing this context to my attention, my partner uses
dialup a lot and it may come in handy to pass on to him.
 
Back
Top