vs.net best practices?

jowilson · Post by **jowilson** » Thu Jun 17, 2004 3:11 pm

My co-worker and I are using Vault 2.0 to manage a couple of medium-sized asp.net projects. One problem we keep running into is what to do with .csproj and .sln files. Do they go into source control? I'd like to cloak them but it doesn't seem that vault allows a person to cloak a single file.

When the files are in source control, if I make a change in vs that modifies the project file and then commit my changes, it uploads my .csproj file. He does a get latest version and bam! Chaos.

We just took the .csproj files out of source control after a while. But there has to be a more elegant solution. What are we missing?

John Wilson

dan · Post by **dan** » Thu Jun 17, 2004 4:22 pm

It should be safe to keep project and solution files under source control. What kinds of errors are you getting when the project file changes?

jowilson · Post by **jowilson** » Fri Jun 18, 2004 1:23 pm

Hmmm... I can't remember, it was several months ago.

We're putting the project files back in Vault and I'll post here when I get a more definite error.