Great ! Always glad to be of assistance. On Jan 18, 1:42 am, jtaylor <[email protected]> wrote: > Your search phrase was on target. Turned out to be an IE issue, not > anything with > VS2003.http://weblogs.asp.net/abdullaabdelhaq/archive/2009/06/01/VS-Debug-Pr... > > Thanks! > > On Jan 16, 2:13 am, Cerebrus <[email protected]> wrote: > > > > > Ahhh... VS 2003... That didn't have the built-in webserver. IIS was > > the only server available. > > > Couple of things to check: > > > 1. Check IIS configuration, particularly related to ASP.NET > > integration. Make sure that the website is configured to run on .NET > > 1.1. > > > 2. Check project configuration (debug mode, etc). > > > 3. Try attaching the debugger to the process manually after opening > > the site in a browser instance. > > > As a search phrase "ASP.NET debugging VS 2003 .NET 1.1" should get you > > a lot of results. > > > On Jan 14, 3:31 am, jtaylor <[email protected]> wrote: > > > > I've inherited a number of webservices still running ASP.NET 2003 > > > (Framework 1.1). I am not allowed to update to a newer Framework, so > > > I'm stuck in VS 2003. I need to debug one of the webservices to track > > > down a bug report. The trouble is that it won't debug. I click Debug > > > and it opens IE but VS seems to disconnect debugging before the page > > > fully loads. > > > > I've Googled every phrase I can think of, but have not found anything. > > > > Does anyone have a suggestion? > > > > Thanks- Hide quoted text - > > - Show quoted text -
-- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
