Hi,
This is my first attempt at remote debugging. I'm moving a website that I've developed on my local machine onto another machine on the network.
If I start the Remote Debugging Monitor on the remote PC and open the website folder through the FileSystem method on the remote PC via my local VS 2005 I can start debugging successfully. The problem then is that because I need to refer to a virtual folder the site crashes and I am unable to test anything.

So, my  question: How do I configure VS 2005 and the debugger so that I can remotely debug but still have the site recognise virtual folders?

Hope this makes sense,

Thanks for any help,

E

Are you moving local site under IIS? If so, you don't need to open it as file system anymore, open it directly via http://url. You don't need to run remote debugging monitor.

Ok, I'm not sure what you mean, (like I say, haven't used VS for remote stuff before) so I'll try and elaborate. I have the original version on my local machine (machine A), which I access through local IIS method.

I now have a copy on another computer on the network (machine B), which runs on the machine B IIS. From my local machine VS I have the option to access the copy on machine B by:

a) opening it through File System - which in conjunction with RDM allows me to debug but messes up virtual folder interaction

b) opening though local IIS - when I try this there doesn't seem to be a way to access any IIS outside of my machine, so no help there.

c) through ftp

d) through url of remote site - doesn't work because I don't have frontpage extensions.

route b) does say 'Local Servers' which makes me think you should be able to access more than just the default localhost, but there doesn't seem to be an obvious way to do that?

Sorry if i'm being dense, thanks for your help!

(d) is officially supported way, you should be able to debug normally with F5.

Opening remote folder as file system is not the same as opening through IIS. Development Web server on your machine will be used then, not remote IIS and DS is much simpler app so some things that work on IIS will not work with Dev Server. This explains (a) as IIS is not used whatsoever if you open Web as file system.

I don't think using remote debugger will help you much. FPSE is what you really need.

Try the following:

Use a) and open the site through the file system. This enables you to open and edit files.

Open the property page for the website in VS. Under the start options tab, select the Use Custom Server option, and enter the URL for the remote server.

It should then tell the remote IIS that it wants to debug, and initiate remote debugging. You'll need admin privelidges on the remote machine.