Visual Studio and Mapped Drives?

[jkelly2956]

We have two developers using VS.NET to access a development server via a network share. When one of them gains access to a Solution and then the other tries to access anything on that share we get the error. "The Local device name is already in use.This connection has not been restored".

This occurs whether the second person is trying to open another project or whether they are just using My Computer to browse the drive.

Any Ideas on what causes this?

 

[lisfolks]

You might want to check the access permissions for that share - it might be set to only allow one user at a time.

 

[jkelly2956]

I have it set to allow 20 Users. Should be more than enough.

 

[lisfolks]

What version of Windows are you using? Also what version of Visual Studio? (And, I presume this share is fully accessible as normal unless someone is using a Visual Studio solution on the share, right?)

 

[chiph]

It sounds like you need a source-code control solution. Visual Source Safe comes with Visual Studio & MSDN subscriptions, but if you've got some money, there are vastly better SCC systems out there (Star Team, PVCS, Perforce, SourceGear Vault, etc).

What this will do for you is allow your developers to check out & lock parts of your code as they need to do work (make code changes). Others are able to get the latest changes up to the point of the lock, so they are able to do builds on their local machine. When the first developer finishes their work, they check in their changes. The other developers are then able to refresh their source and use the new code.

Since each developer works off their local machine, you don't have any network locking issues, nor do you have developers overwriting each other's changes. Highly recommended.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[jkelly2956]

lisfolks --The development server we are connecting to is running win2003 server. The desktops have Win XP prof and are using VS.NET ver 7.1.3088 / .NET FRAMEWORK version 1.1.4322

chiph -- We are using VSS but I don't think that is the problem. We are not even working on the same files/website. I am doing web development and he is doing data import via a .NET exe. We do keep the sln files on the development server and place the other source files under VSS.

The weird thing is that once one of us opens a project in VS.NET the other can go and browse the share via Windows explorer/TextPad/Photoshop and it will give you the error stated above. Sometimes it will let you drill down a few dir and then kick you out telling you the share is no longer available. We can ping the server during these times so I don't think the network is the issue. It is like VS.NET locks the whole share.