Keeping Visual Studio Projects on a Network Drive

Question

We just did a move from storing all files locally to a network drive. Problem is that is where my VS projects are also stored now. (No versioning system yet, working on that.) I know I heard of problems with doing this in the past, but never heard of a work-around. Is there a work around?

So my VS is installed locally. The files are on a network drive. How can I get this to work?

EDIT: I know what SHOULD be done, but is there a band-aid I can put on right now to fix this and maintain the network drive?

EDIT 2: I am sure I am not understanding something, but Bob King has the right idea. I'll work with the lead web developer when he gets back into the office to figure out a temporary solution until we get some sort of version control setup. Thanks for the ideas.

Answer 1

While we do use Source Control, we do also run all our projects from Network Drives (not shared directories, private directories on network drives). The network drives are backed up nightly, and also use Volume Shadow Copy, so if you need to revert to something before it made it's way to SC, then you can.

To get projects to run correctly with the right permission, follow these steps.

Basically, you've just got to map the shared directory to a drive, and then grant permission, based on that Url, to all code. Say you map to "N:", then use "N:*" as your Url pattern. It isn't obvious you need to wildcard, but you do.