Feature Request: Tortise clone
Moderator: SourceGear
-
- Posts: 10
- Joined: Fri Dec 03, 2004 5:48 pm
Feature Request: Tortise clone
I know this topic has come up before, but I wanted to post a fresh one to indicate my vote for explorer integration.
Regards-
Eric
Regards-
Eric
+1 vote for too me
We are considering switching to subversion for this reason.
It is much easier in TortoiseSVN to see and add unversioned files. I know the vault client has "Detect new files to add" but it is lacking in that area. There isn't a per-project ignore like SVN has (so I can ignore bin and obj directories). I can set that in Files/folders to exclude but with SVN I can set that per folder/project and my entire team gets the setting. Also, unversioned files just show up under "changes made" (Tortoise equivalent of Pending Change Set) without having to do through a separate detect new files to add step.
Another big issue we have with vault is that it doesn't detect folders. The ghosted folders helps a little but it is still very easy to get burned by forgetting to add a new folder. With ghost folders you have to go through each subdir to be sure you didn't miss anything. with TortoiseSVN they are just there in the changes made list.
I guess those features don't have to be exclusive to a shell integrated client, but the overlay icon stuff is cool too.
Don't get me wrong, Vault rocks, just these two little things seem to constantly come up in our team. I thought about using the API to make my own shell integration client but my shell skills are lacking and there are issues with CLR shell extensions (not everyone wants the entire CLR loaded in memory with explorer, can only have one version of the CLR loaded per process so if someone has a different .net shell extension loaded and it's a different version it is a race to see which version gets loaded)
We are considering switching to subversion for this reason.
It is much easier in TortoiseSVN to see and add unversioned files. I know the vault client has "Detect new files to add" but it is lacking in that area. There isn't a per-project ignore like SVN has (so I can ignore bin and obj directories). I can set that in Files/folders to exclude but with SVN I can set that per folder/project and my entire team gets the setting. Also, unversioned files just show up under "changes made" (Tortoise equivalent of Pending Change Set) without having to do through a separate detect new files to add step.
Another big issue we have with vault is that it doesn't detect folders. The ghosted folders helps a little but it is still very easy to get burned by forgetting to add a new folder. With ghost folders you have to go through each subdir to be sure you didn't miss anything. with TortoiseSVN they are just there in the changes made list.
I guess those features don't have to be exclusive to a shell integrated client, but the overlay icon stuff is cool too.
Don't get me wrong, Vault rocks, just these two little things seem to constantly come up in our team. I thought about using the API to make my own shell integration client but my shell skills are lacking and there are issues with CLR shell extensions (not everyone wants the entire CLR loaded in memory with explorer, can only have one version of the CLR loaded per process so if someone has a different .net shell extension loaded and it's a different version it is a race to see which version gets loaded)
I have a very similar need... There are a couple open source projects I will admin and it would be really convenient if I could host them on Vault, but the users would need to have a svn-like interface (command line) and to a lesser degree the TortoiseSVN-like interface mentioned here.
I'm not asking that you make a svn interface layer, but maybe it would be something to kick around when you guys are talking long-term issues... The real long-term question is just how much do you want Vault to work in other operating systems, and how Vault would work in a SVN-dominated world.
I'm not asking that you make a svn interface layer, but maybe it would be something to kick around when you guys are talking long-term issues... The real long-term question is just how much do you want Vault to work in other operating systems, and how Vault would work in a SVN-dominated world.
gabriel magana-gonzalez