Hello All,
We’ve been struggling to set up remote debugging of ASP.Net 2.0 in Visual Studio 2005. We don’t have IIS installed on our machines and we still support a lot of classic ASP, so our local ASP.NET development server is not an option. I’ve done a lot of Googling and tried a lot of different things but ultimately I can’t seem to get the ASP.NET worker process to appear in the Attach to Process dialog. No breakpoints are being hit when I attach to the page on the specific iexplore.exe process (works for javascript, but not for server-side code). Here is our technical setup:
- Dev Web Server: Windows Server 2K3 Web Edition, IIS 6, VS2005 Remote Debugger installed
- Client: Win XP Pro, VS2005 Pro
- Both client machines and dev web server are on the domain (I log into the web server through UltraVNC using the same domain account that I log into my machine) and our domain accounts are not administrators on any machines
- Currently need to login (using accounts stored in the database, not domain accounts) thru classic ASP screens to get to ASP.NET screens (we’re still in the early stages of migration to .NET), so direct access is not possible from a security standpoint
- aspx and aspx.vb files are developed as individual files (no web site project) using VS2005 on our client machines through a network share on the dev web server with no direct compile (As an experienced ASP.NET developer who works with developers with classic ASP mentality, I don’t agree with this setup but this is the wrong forum for a political rant!)
Any help would be greatly appreciated, as reliable resources on this subject seem to be hard to find. I’d rather not double the size of my code by putting Trace statements everywhere (this is all too quickly becoming the web development standard here and it scares me!).
Thanks in advance,
Mike
We’ve been struggling to set up remote debugging of ASP.Net 2.0 in Visual Studio 2005. We don’t have IIS installed on our machines and we still support a lot of classic ASP, so our local ASP.NET development server is not an option. I’ve done a lot of Googling and tried a lot of different things but ultimately I can’t seem to get the ASP.NET worker process to appear in the Attach to Process dialog. No breakpoints are being hit when I attach to the page on the specific iexplore.exe process (works for javascript, but not for server-side code). Here is our technical setup:
- Dev Web Server: Windows Server 2K3 Web Edition, IIS 6, VS2005 Remote Debugger installed
- Client: Win XP Pro, VS2005 Pro
- Both client machines and dev web server are on the domain (I log into the web server through UltraVNC using the same domain account that I log into my machine) and our domain accounts are not administrators on any machines
- Currently need to login (using accounts stored in the database, not domain accounts) thru classic ASP screens to get to ASP.NET screens (we’re still in the early stages of migration to .NET), so direct access is not possible from a security standpoint
- aspx and aspx.vb files are developed as individual files (no web site project) using VS2005 on our client machines through a network share on the dev web server with no direct compile (As an experienced ASP.NET developer who works with developers with classic ASP mentality, I don’t agree with this setup but this is the wrong forum for a political rant!)
Any help would be greatly appreciated, as reliable resources on this subject seem to be hard to find. I’d rather not double the size of my code by putting Trace statements everywhere (this is all too quickly becoming the web development standard here and it scares me!).
Thanks in advance,
Mike