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?