>I'm not sure if I'm even posting this question in the correct section, but here goes...
>
>Two question about Visual SourceSafe in a Visual Studio.NET environment...
>
>1) Let's say we have a multi-developer project, where the project is stored in VSS on the network. If a developer 'checks out' a set of code from the network, does that mean that the project on the network stays 'open'? Reason I ask is that I'm trying to determine if our nightly backup process would be able to backup the project, if indeed the project stays 'open' if someone has checked out modules after hours.
>

Projects do not stay open. Backups are no problem.

>2) This might seem really stupid to ask, but...if a developer does a 'GET' from a VSS project (as opposed to checking it out), I've been told that what the developer is grabbing is a 'read-only' reference. Is it possible for a developer to do a 'GET' of a module, pull it down to his/her local machine, and modify/experiment with the local version...even if there's no intention to synchronize changes? (Reason for asking is that I've been told that if a developer does a 'get', what they 'get' is read-only and there's no way to do any modifying/experimenting...I find this pretty hard to believe).
>

There is an option in VSS under Tools, Options Local Files where you can uncheck the "use read only flag for files that are not checked out".