I have a team of three developers working on the same Web Application Project web site. Each of us has a different working folder on our local drives and I am encountering some issues I need to understand:
1) When one of use wants to add a new page to the project, it appears that we must check out the entire project or at least the .csproj file, add the page and then check the .csproj file back in. Is this correct?
2) When we checkin the changed code, we must not checkin the bin folder or anything in it. If we do, nobody else can compile their code. Again, is this correct?
Multiple developers working on same Web Application Project
Moderator: SourceGear
Re: Multiple developers working on same Web Application Proj
The project file maintains information on what items are in the project. So if you add a file, the project file is modified by Visual Studio. In most cases, a modified file is automatically checked out by Vault. When the project file is checked out because of project modifications, then checked in, other users will be able to do a Get Latest so everyone has the same verison of the project file.When one of use wants to add a new page to the project, it appears that we must check out the entire project or at least the .csproj file, add the page and then check the .csproj file back in. Is this correct?
Generally the results of compiling, such as exe's, etc, bin folders, and user-specific files are not put under source control. The source code files that generate these results are put into source control.When we checkin the changed code, we must not checkin the bin folder or anything in it. If we do, nobody else can compile their code. Again, is this correct?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager