We currently have a few different developers working on a project. Currently they log into our dev server using terminal services use Visual Studio (2k5) dir ectly on the server. We may have a few different people at a time, logged into their own account developing at the same time.

We have our projects in VSS but everyone opens up the same project. So we're all actually using the same physical files. So if someone has a file checked out, occassionally someone else has been able to edit it because it is not marked as read-only. There are warnings in the VS IDE but ti has caused some problems.

What we want to do is have everyone using their own copy of the files. So i have to create a folder for each user and load the project into that folder for that user. But that also means I would have to create seperate websites for each one referencing seperate virtual directories, is that correct?

Then save the solution, the project files, and teh website virt directories physical paths all into each users own folder.

That should work, shouldn't it?

Yes, I would highly recommend giving everyone their own working directories as you describe. Working on the same physical files almost defeats the purpose of using source control

Yes, I would highly recommend giving everyone their own working directories as you describe. Working on the same physical files almost defeats the purpose of using source control

How do you get the individual developer's updated code integrated into source code?

You can merge the files later:
http://msdn.microsoft.com/en-us/library/ms181073(VS.80).aspx

---

Catherine Sea
Version Control Software | Software Configuration Management Solution