index > Team Foundation Server - Administration > Removing project files from source control ?

Removing project files from source control ?

Can i remove project files from source control ? By this i mean files like app.config, that are particular for each computer - it's really bothering when you get the latest version of an entire project and the above mentioned file gets overwritten.

10x

Marius Onofrei

You can just delete the file, but you can also install a custom check-in policy to make sure somebody checks it back in again. Over to the Yoda of check-in policies again, James Manning:-

http://blogs.msdn.com/jmanning/archive/2006/02/02/523125.aspx

It would be nice if there was an "ignore from source control" capability, but there isn't in V1 I'm afraid.

http://www.woodwardweb.com

Martin Woodward

I've tried deleting the file, but the file also gets unloaded from the project, so it's no good.
I'll try with the custom check-in policy !

10x a lot !

Marius Onofrei

Then again - started thinking about that - i would still need to unload files from my projects because i would still need to delete the files from SourceControl.

I could leave a copy under SourceControl, but when a persona gets a latest revison on the entire project, the app.config (or whatever) would get overwritten on the local computer - no good again.

Can i somehow mark files as being disabled for get revison ?
I cannot see another solution.

10x again !

Marius Onofrei wrote:
I've tried deleting the file, but the file also gets unloaded from the project, so it's no good.
I'll try with the custom check-in policy !

10x a lot !

Marius Onofrei

You could rename the file to something like app.config.template. The first time the developer does a get latest it will rename the file on their file system. If they then go into Explorer (in Windows) and copy the app.config.teamplate, calling it app.config - the file will not get overwritten from now on because the Team Foundation Server doesn't know about it.

Hope that helps - obviously you'll have to manually manage the case when new properties are added to the app.config.teamplate file...

http://www.woodwardweb.com

Martin Woodward

Yes i've already considered this option - yet - i would have to add the app.config file (after renaming it on the local computer) to the project, which automatically adds the file to the SourceControl pending changes list - and with a Check-in we are right back where we've started :-); sorry for bringing out the bad news.

10x for your patience - there must be an answer to this!

Martin Woodward wrote:
You could rename the file to something like app.config.template. The first time the developer does a get latest it will rename the file on their file system. If they then go into Explorer (in Windows) and copy the app.config.teamplate, calling it app.config - the file will not get overwritten from now on because the Team Foundation Server doesn't know about it.

Hope that helps - obviously you'll have to manually manage the case when new properties are added to the app.config.teamplate file...

M.

Marius Onofrei

After you do an "Add, Existing Item..." and it automatically pends an add for the app.config, try selecting the app.config file and doing "Undo pending change" on that file only.

http://www.woodwardweb.com

Martin Woodward

Got it right this time !

It was something like you've suggested - i've removed the App.config from SourceControl and then undone changes in the .csproj, the app.config file in the project became invalid, moved another one in the project folder - AND ALL DONE !

Thank you for your help !
Bye !

Marius Onofrei

reply 8