Shared Source for Visual Studio 2008 takes too long in loading

We have several projects for Visual Studio 2008 Professional, SP 1 (VB.Net) which are developed by 2 or 3 people.

The necessary files are on a shared network folder, and we are using SourceSafe 6.0 to share the code. This is generally working ok.

The problem is: As soon as one developer has opened the project (and is in a debug or compile process), it will take ages for the 2nd person to startup the Project. Everything is just painfully slow, and this problem remains until the 2nd person changes the assembly name. But, it takes ten minutes just to be able to get into the screen to change the assembly name.

Is there something wrong about the way we mapped our SourceSafe?
Why does VS 2008 get slow if the Project is debugged on another station?
Or might there be a way to change the assembly name automatically to work around this problem?
BarepAssetsSys AdminAsked:
Who is Participating?
Éric MoreauConnect With a Mentor Senior .Net ConsultantCommented:
>>The necessary files are on a shared network folder,

When you talk about "necessary files", you talk about VSS files right? To be able to share project with VSS, yes it is generally installed on a server.

But I hope that your "necessary files" are not the files you retreived from VSS. Your working folder should be a local drive (private to each developer).

If each developer has his own local folder, VSS is not aware of what's happening locally and will not slow down operations.
BarepAssetsSys AdminAuthor Commented:
Actually, everything is on the shared network drive, the whole project and the VSS files.

So we all use the same "Checkout Folder".

I will try and setup different working folders for each developer on the harddrive like you said, and check if that makes a difference.
Éric MoreauSenior .Net ConsultantCommented:
>>So we all use the same "Checkout Folder".

Never do that, you are running after trouble!

Each developer needs his own local folder (to be isolated from others and for speed).
BarepAssetsSys AdminAuthor Commented:
After some testing I agree that using seperate CheckOut Folders is a great idea...
(and you'll get some points for this)

We still have the problem I mentioned at the start>
If one user is in a debug session, even if he has nothing checked out, the project is very slow while getting the sourcesafe files for the other user.

Our SourceSafe is 6.0d, maybe the version is too old?
Éric MoreauSenior .Net ConsultantCommented:
When you start a debug session, source safe is totally inactive. Your problem is not there. I have now switched to VSS 2005 but there was a time when I was using VSS 6.0d with .Net projects and never had that kind of problems.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.