this product is fantastic. Being a VSS oldie I got going right away with sourcegear vault.
My only suggestion for improvement so far
Why isn't *.config and *.csproj selected by default when I choose to add a whole directory?
I guess it's not a big deal when I really get going but now I am adding all my hundreds of projects and VS 2005 solutions into Vault...
I know we can change the Exclude filter but by default IMHO those should be included??
files to be selected
Moderator: SourceGear
-
findhealthinfo.net
- Posts: 3
- Joined: Wed Apr 02, 2008 9:42 am
- Contact:
Are you adding these in using the Vault GUI client? If so, then Vault is pretty oblivious about what goes together.
If you plan on using IDE integration, you may get better results by instead adding those through Visual Studio by using the IDE integration. Then VS will decide what goes in and send the commands to Vault.
If you won't be using IDE integration, then the method you are using is fine. Vault just doesn't know what goes with a project. It has to be told.
If you plan on using IDE integration, you may get better results by instead adding those through Visual Studio by using the IDE integration. Then VS will decide what goes in and send the commands to Vault.
If you won't be using IDE integration, then the method you are using is fine. Vault just doesn't know what goes with a project. It has to be told.
-
findhealthinfo.net
- Posts: 3
- Joined: Wed Apr 02, 2008 9:42 am
- Contact:
thanks beth.
Yes I am not using IDE integration so I am just suggesting that (after a clean install) the Vault GUI client sholdn't exlude .config and .cproj files. I learned it the hard way so to speak.
"It has to be told.". But somehow it has already been told by you, by default, to EXCLUDE those files. My suggest is that after install, by default, those should *not* be exluded.
Anyway, just a friendly suggestion from me to you, as I said no real issue at all
Yes I am not using IDE integration so I am just suggesting that (after a clean install) the Vault GUI client sholdn't exlude .config and .cproj files. I learned it the hard way so to speak.
"It has to be told.". But somehow it has already been told by you, by default, to EXCLUDE those files. My suggest is that after install, by default, those should *not* be exluded.
Anyway, just a friendly suggestion from me to you, as I said no real issue at all
Check what is set in your Admin web page. There is a list of items that should be excluded. I don't think those are in there by default. It should only be things like dll or bin type files.
By default, the exact file types that should be listed are:
*.clw; *.config; *.dca; *.dll; *.dsw; *.exe; *.hlp; *.incr; *.ncb; *.opt; *.pdb; *.plg; *.scc; *.suo; *.user; *.vbw; *.webuser
So, you have it right with the config file, and you can remove it from that list, but the .csproj shouldn't be listed there.
By default, the exact file types that should be listed are:
*.clw; *.config; *.dca; *.dll; *.dsw; *.exe; *.hlp; *.incr; *.ncb; *.opt; *.pdb; *.plg; *.scc; *.suo; *.user; *.vbw; *.webuser
So, you have it right with the config file, and you can remove it from that list, but the .csproj shouldn't be listed there.