Plus you will need to install Remote Debugging on the webserver. Are you
sure you want to change your developing instance over to a shared server.
It is much slower to debug, and to build and test. Also like Vko said, when
one developer is debugging the server no one else will be able to do
anything on the shared webserver.
In my group we have 5 developers. We all develop on our local machine with
a remote Sql2000 server. We also have a dev server. When a developer has
completed a change, we put out the "dev" site to the development machine.
When the "dev" changes have been approved, we will build a "release" version
to be placed on the remote production web server.
HTH,
bill
"gemel" <jo***@glenavon1.demon.co.uk> wrote in message
news:d8********************************@4ax.com...
Up until now I have been developing my ASP .NET web applications on
the same machine as the client and then using 'Copy Project' or Web
Setup to transfer the application.. This also included the SQL 2000
Server.
Now I wish to operate Visual Studio on my client but to use a Web
Server and Sql Server on another part of my network. What changes are
required and what impact will this have in terms of debugging?
Regards
John L
