Solved

Shared Source for Visual Studio 2008 takes too long in loading

Posted on 2008-10-08
5
328 Views
Last Modified: 2013-11-26
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?
0
Comment
Question by:BarepAssets
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 70

Accepted Solution

by:
Éric Moreau earned 400 total points
ID: 22668290
>>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.
0
 

Author Comment

by:BarepAssets
ID: 22668351
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.
0
 
LVL 70

Expert Comment

by:Éric Moreau
ID: 22668393
>>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).
0
 

Author Comment

by:BarepAssets
ID: 22680342
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?
0
 
LVL 70

Expert Comment

by:Éric Moreau
ID: 22680402
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.
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes relatively difficult and non-obvious issues that are likely to arise when creating COM class in Visual Studio and deploying it by professional MSI-authoring tools. It is assumed that the reader is already familiar with the cla…
Article by: gr8gonzo
Git can be a complicated version control system for beginners, but it definitely is one of the best ones out there. Since this article assumes that you're starting at square one, it will skip over things that Git -can- do and will focus on the typic…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question