More data - this is wierd.
I've got a folder in visual source safe with 9 files in it. I get prompted for "Get Latest Version" 34 times!!!! Some folders it doesn't prompt "Get Latest Version", others it does.
Turning off the Advanced "show dialog boxes" has no effect.
Why is "Get Latest Version" so poor?
Moderator: SourceGear
mike:
i just attempted this... here are the steps i took for a successful get.
1 ) did a check to see if there were no working folders assigned. i used the command line client's -listworkingfolders command, and removed all working folders, so i would be starting fresh.
2 ) started vs.net. changed the advanced source control options -> logged into my vault server, and turned OFF always show get dialog. clicked OK to accept the changes on the vault dialog and vs.net options dialog.
3 ) from vs.net -> invoked open from source control.
4 ) chose the repository path where the vault solution file exists ($/trunk/vault/src), and set a brand new working folder (c:\work\project\vault\src). it asked me to create c:\work\project\vault\src, which i did. since part of this was a web project, it asked me for the local url for the vault server, which i provided.
5 ) sat and waited (over a 56Kbps from home) connection for the vault project to download to my machine.
6 ) after 10 minutes (but no "get dialogs"), the project was up and ready to go.
7 ) i reset the advanced options in step 2 to always show me the get dialog on get latest.
8 ) for future sessions of vs.net, i now use file->open and open the c:\work\project\vault\src\vault.sln file found locally on disk.
in sum, the "always show dialog at get latest" is doing just what it says --- always showing the dialog during a get latest. this is somewhat irksome.
in my every day use, i like the dialog to show up, during gets on files i have already retrieved, as sometimes i want it to overwrite my working copy, but at other times i may want to merge in those changes.
when the file doesn't even exist, it would be nice to dismiss this dialog. i've logged a feature request to see if there is a way to not show this dialog, if the file has never been retrieved to the working folder. perhaps there is some other way to disable the get latest dialog but only during these first get operations.
do the steps i outlined above work for you?
i just attempted this... here are the steps i took for a successful get.
1 ) did a check to see if there were no working folders assigned. i used the command line client's -listworkingfolders command, and removed all working folders, so i would be starting fresh.
2 ) started vs.net. changed the advanced source control options -> logged into my vault server, and turned OFF always show get dialog. clicked OK to accept the changes on the vault dialog and vs.net options dialog.
3 ) from vs.net -> invoked open from source control.
4 ) chose the repository path where the vault solution file exists ($/trunk/vault/src), and set a brand new working folder (c:\work\project\vault\src). it asked me to create c:\work\project\vault\src, which i did. since part of this was a web project, it asked me for the local url for the vault server, which i provided.
5 ) sat and waited (over a 56Kbps from home) connection for the vault project to download to my machine.
6 ) after 10 minutes (but no "get dialogs"), the project was up and ready to go.
7 ) i reset the advanced options in step 2 to always show me the get dialog on get latest.
8 ) for future sessions of vs.net, i now use file->open and open the c:\work\project\vault\src\vault.sln file found locally on disk.
in sum, the "always show dialog at get latest" is doing just what it says --- always showing the dialog during a get latest. this is somewhat irksome.
in my every day use, i like the dialog to show up, during gets on files i have already retrieved, as sometimes i want it to overwrite my working copy, but at other times i may want to merge in those changes.
when the file doesn't even exist, it would be nice to dismiss this dialog. i've logged a feature request to see if there is a way to not show this dialog, if the file has never been retrieved to the working folder. perhaps there is some other way to disable the get latest dialog but only during these first get operations.
do the steps i outlined above work for you?
Jeff Clausius
SourceGear
SourceGear
Jeff,
I am finally checking out a new tree- I avoid this now because i know that vault will lead me through the gazillion clicks.
I followed your steps to a tee, but it didn't change Vault's behavior at all.
Notes:
* I used to commandline to do LISTWORKINGFOLDERS and UNSETWORKINGFOLDERS. In general, you want this property to just "inherit" from the top-level folder. I found that somehow I had accidentally set about 4 folders to not-inherit. I was optimistic this would be the cause of the problem, so I UNSET all of them - until LISTWORKINGFOLDERS showed me it had none:
<vault>
<listworkingfolders />
<result success="yes" />
</vault>
* I have the advanced "show get dialog" unchecked already. For me, it won't let me change them from the VS.NET side anyway. They are grayed out. but, it was already set as you recommended.
* Invoked the "Open from source control" I selected a brand-new-doesn't exist-yet directory.
* It asked me "do you want to create this directory...'
* Now I'm back into the thousand-click-loop-routine.
What does it mean when it pops up this Get Latest Version dialog? Does it think it needs to merge? Is there something i can check about my source files that is whacked? Were these files added to the repository differently than other files?
Its been several weeks now. Maybe you have a patch for this?
Thanks,
Mike
I am finally checking out a new tree- I avoid this now because i know that vault will lead me through the gazillion clicks.
I followed your steps to a tee, but it didn't change Vault's behavior at all.
Notes:
* I used to commandline to do LISTWORKINGFOLDERS and UNSETWORKINGFOLDERS. In general, you want this property to just "inherit" from the top-level folder. I found that somehow I had accidentally set about 4 folders to not-inherit. I was optimistic this would be the cause of the problem, so I UNSET all of them - until LISTWORKINGFOLDERS showed me it had none:
<vault>
<listworkingfolders />
<result success="yes" />
</vault>
* I have the advanced "show get dialog" unchecked already. For me, it won't let me change them from the VS.NET side anyway. They are grayed out. but, it was already set as you recommended.
* Invoked the "Open from source control" I selected a brand-new-doesn't exist-yet directory.
* It asked me "do you want to create this directory...'
* Now I'm back into the thousand-click-loop-routine.
What does it mean when it pops up this Get Latest Version dialog? Does it think it needs to merge? Is there something i can check about my source files that is whacked? Were these files added to the repository differently than other files?
Its been several weeks now. Maybe you have a patch for this?
Thanks,
Mike
The "Always display command dialog on Get Latest" option should never be disabled when accessing advanced options in the IDE, so this seems suspicious.mike wrote:
* I have the advanced "show get dialog" unchecked already. For me, it won't let me change them from the VS.NET side anyway. They are grayed out. but, it was already set as you recommended.
Just to be clear, the options are accessed from within Visual Studio, Tools->Options->SCC Provider->Advanced button, which brings up Vault options within VS.Net
You might be looking at Command Dialogs->Get Latest Version, which would always be grayed out and disabled when accessed from the IDE. The "always display command dialog on Get Latest" is in the General options section. (They are different options because one is IDE only, whereas the Command Dialogs section will affect both the GUI and IDE client). If that is on, turn it off, and see whether you get the same results.
Finally solved my issue
I switched from Vault back to CVS. Its a bummer - I think I wasted the $800 on vault, I doubt I'll ever get it back.
Guys, vault is just beta code. Way too many bugs, gotchas and frustrations. Its just not worth it.
If you could do a dump of my config file and then help me get to the bottom of the issue, I probably wouldn't have switched off. But instead, we're here with the same problem for 6 weeks, and everyone on the CS side is just scratching their heads saying "umm....."
And this isn't my only issue. Every time I touch Vault - it gets confused. Spent more time dealing with vault than coding over the last week.
When you do decide to move out of beta - please add some hooks so that you can troubleshoot better.
Good luck,
Mike
Guys, vault is just beta code. Way too many bugs, gotchas and frustrations. Its just not worth it.
If you could do a dump of my config file and then help me get to the bottom of the issue, I probably wouldn't have switched off. But instead, we're here with the same problem for 6 weeks, and everyone on the CS side is just scratching their heads saying "umm....."
And this isn't my only issue. Every time I touch Vault - it gets confused. Spent more time dealing with vault than coding over the last week.
When you do decide to move out of beta - please add some hooks so that you can troubleshoot better.
Good luck,
Mike
Sorry to hear that mike - I assumed things were going fine, since we had not heard back from you on the last post.
It is true that it is hard to get the IDE setup and working, but we will have to disagree on the beta code statement.
Since this thread was started, we have posted a number of knowledge base articles about IDE setup and options. If anyone is having the same problems mike had, please see our knowledge base index at http://support.sourcegear.com/viewtopic.php?t=792 before setting up projects in the IDE, or if you are having troubles with IDE options. If you still have problems, post to this forum, and we'll try to track it down as best we can.
It is true that it is hard to get the IDE setup and working, but we will have to disagree on the beta code statement.
Since this thread was started, we have posted a number of knowledge base articles about IDE setup and options. If anyone is having the same problems mike had, please see our knowledge base index at http://support.sourcegear.com/viewtopic.php?t=792 before setting up projects in the IDE, or if you are having troubles with IDE options. If you still have problems, post to this forum, and we'll try to track it down as best we can.