I just started working at an organization using Vault. One problem we are having is that there are three of us doing development in Visual Studio 2005, often on different parts of the same website. When we are working on code modifications we use a local copy of SQL Server 2005 to test against. To do this, we change a line in our web.config file to point to our personal copy of the database. The problem is that in order to modify this file, we have to check it out. While we have it checked out, if one of the other team members tries to rebuild the solution, it sees that the web.config file is checked out and won't let you rebuild the solution until that file gets checked back in. Then the other team member has to change the web.config file again for their own settings in order to rebuild the solution. You get the idea --- we are always fighting over this particular file...
Botom line, can we omit this particular file from source control entirely? If so, how do we do it?
Omitting specific file from source control
Moderator: SourceGear
No option to remove from source control
---> I am working in Visual Studio 2005. When I right-click the file in Solution Explorer there isn't an option to remove it from source control. When I look at the file in the Vault Client, there isn't that option there either. I know I should be able to do this --- any idea where else to look?Beth wrote:I think that you should be able to right click the file and tell it not to be under source control.
What are you using for a build?
I'd guess you want to leave the file under source control, because your web.config probably has information you don't want to lose.
So another route to try would be to leave the file checked-in, and just make the file writable on disk. The Vault UI will show the file with a "Renegade" status.
Then, if one of you makes a change that actually should be in the file, you can check out the file "for real", make the change, and check it back in. Then the others can get latest or merge the file, and only make your local changes once in a while.
So another route to try would be to leave the file checked-in, and just make the file writable on disk. The Vault UI will show the file with a "Renegade" status.
Then, if one of you makes a change that actually should be in the file, you can check out the file "for real", make the change, and check it back in. Then the others can get latest or merge the file, and only make your local changes once in a while.
David Thompson
JELD-WEN, inc.
JELD-WEN, inc.
Making file writeable on disk??
Thanks very much for your reply to my post.
OK, the "Renegade" approach sounds like it would work. I agree that having a copy in source control is a better solution than omitting it from source control completely. I looked at the file in Windows Explorer and it isn't marked as read-only at that level, so I am assuming it is only the Vault Add-In that is keeping me from editing it without checking it out first. How do I make a file writeable without checking it out from source control?
OK, the "Renegade" approach sounds like it would work. I agree that having a copy in source control is a better solution than omitting it from source control completely. I looked at the file in Windows Explorer and it isn't marked as read-only at that level, so I am assuming it is only the Vault Add-In that is keeping me from editing it without checking it out first. How do I make a file writeable without checking it out from source control?