Not quite, but nice approach, though. I have thought about your suggestion too. The server is running IIS and .NET FW 1.1 and all the files are there and the site is up and running on the server. What I want to avoid is setting up local sites on all developer clients, because that's what VS.NET demands with web projects. If I can somehow point each machines "localhost" to the server IP then the VS.NET clients would open the site directly from the server, instead of returning "...the path ... does not correspond to the URL ...The two need to map to the same server location."

Still just a theory, but I believe there is a way.

>Danijel,
>
>If I understand this correctly, the Win2k server where your source files are located is not running IIS and the .NET Framework, but the files are available as a network share.
>
>If this is the case, go into IIS Manager on your laptop, open the properties of the project's web site under wwwroot, and change the location to point to the network share path (don't forget to click the radio button that says "network share"). Once this is done, the application will run on IIS in your laptop but it will retrieve all of the files from the Win2K server.
>
>
>>I'm developing a .net web app. The coding will be done on my laptop with all the tools in place, but the files are shared out off another W2K server in the network where the app is running, but no tools are installed there.
>>
>>Now, as most are familiar with, opening a project file from local laptop won't work 'cause the Studio will try to open the web project with localhost/app URL.
>>
>>What are the options here in opening the project localy? I was thinking it might be possible to alter the hosts file and change the localhost to point to the dev.server's IP, but that didn't turn out to go that simple. Any thoughts on this? And are there other alternatives?
>>
>>Thanks a lot.