Team System & Read Only Files
Probably because of Source Safe, Team System Source Control believes in read only files, which means that just about everything that I do with code generation started to break. Part of my build process is generating quite a bit of functionality, but now I need to special case for the read only, and then remember to check in any changes that were made.
Is there such a thing as Tortoise for TeamFoundation? It drives me crazy that I need to remember that I put a file in the file system, since TF will gladly ignore anything that I didn't explicitly told it to check, and this will break the build for other people, without me being aware of it until the shouts starts.
Comments
I'm in protest of TS :)
I like Subversion with TortoiseSVN, it's become my favorite source control setup :)
Hi Oren,
I agree its a m-PITA. But me complaning will not help you. So one hint: Have your tried the "team foundation power toys"? You can download it from MS. It has a command "online" that looks at your workspace and will submit add commands for new files, edit commands for changed ones and even delete commands for missing ones. Not perfect, but workable.
Anyway you could still call the "tf.exe" command line tool in your build process to do source control commands.
ralf
I don't like the build going to the source control for stuff.
I especially don't like it when all devs are running it in the same time...
I will check the power toys, I think that I will remove the binding from VS and just work completely from the command line.
Have you tried AnkhSVN? It became a final version (non beta) recently.
I tried it, and I didn't like it very much, I got very used to working from explorer with tortoise
VisualSVN works very well for us. It basically drives TortoiseSVN from within Visual Studio.
Comment preview