Sharing Development

My company is using Source Safe to check files in and out during initial development. However, we cannot find a way to work on the same projects at the same time because our solution and project files are overwriting each other and causing problems. Does anyone know of a way for two people to work on different pages of the same solution at the same time and not worry about conflicts in the solution and project files?

To be more blunt, is it possible for mutliple people to work on the same project and share solution and project level files? I find this to be the biggest problem with ASP.NET development.Hi,

we currently develop with 3 coders on the same asp.net project while the business and data tiers are written by some other developers. We use source safe and don't have any problem. What the person who's responsible for the VSS databases did was that he turned of multiple checkouts so that only one person can check out 1 file at the same time. So we work independent on different web forms and user controls that we check in on a regular basis.

Grz, Kris.
Micro soft has a paper on Team development with .Net and VSS... I don't have the link handy...

A short answer to your question is... Only check out the SLN file when you need to... Or don't ever put the sln file into source safe... then each developer can have their own solution set up on their local machine...
I guess I need to find out more about what the solution file does. Every time we start to use different solution files, we can never get the project back together correctly. New files are always missing and we get various error messages. Do you happen to know when the solution of project files need to be changed for a project? I would assume when adding files, but what about compiling the project to debug?
It's not that we have an issue with sharing individual files, it's all the overhead files (solution, project, etc.) that seem to mess our project up when used by different people. For example, I need these files if I'm adding new files and assemblies to the project (I assume at least.) If another developer is making changes and has a separate solution file on his machine, how would we get the correct set of files back together? Do you not run into problems using different sets of these types of files?
We have the solution and project files stored in vss but have the policy that anyone who uses it, when adding a new webform, first has to do a rebuild so that the added code doesn't break the build, and then checks it in asap. Or else she/he will hear it from the others :-) .

Grz, Kris.
From the top of my head...

Solution files store info about which projects belong to the solution...

Project files store info about which files(vb, aspx, ...) belong to the project...