But I dont want local debugging, I want Semi-Isolated Development that
I know was possible in studio 2003; developers have local copies of
files but check-ins and debugging occurs on central server (the working
copy).
When opening a web project from sourcesafe in 2003 you got a dialog
prompting for Working Location (e.g
http://devserver/website). Then
behind the scenes files would get updated on the working site.
Doing the same in 2005 and you get no dialog and it appears you can
only work in Isolated mode and updating the central development site
would be a manual process, lovely!
Have a look at this (applicable to 2003):
http://msdn.microsoft.com/library/de...lStudioNET.asp
Cowboy (Gregory A. Beamer) wrote:
Download the bits locally and aim the solution file to the local bits. You
should also put the local versions into IIS locally (you can do this with
web sharing under Windows Explorer properties).
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
"smurph" <sm******@hotmail.comwrote in message
news:11**********************@k70g2000cwa.googlegr oups.com...
We have a web application project, currently this is in sourcesafe.
What I want is the developers to edit, debug and save the files locally
on their own machine, then when they check in the file it automatically
updates the master website. This last bit I cant work out how to do?
How do I configure this? It was so easy in Interdev.