Random change of working folder

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Random change of working folder

Post by Dino » Tue Oct 25, 2005 7:20 pm

I just saw this occur right before my eyes! My working folder was correct, and I was about to get latest on a file... when suddenlly all files are missing, and the working folder was changed! It changed to this:

C:\Documents and Settings\deanc\My Documents\Visual Studio Projects\ExtraMile\iChange\NewHollandImport

When it was (Correctly) this:

C:\Documents and Settings\deanc\My Documents\Visual Studio Projects\ExtraMile\iChange

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Tue Oct 25, 2005 7:22 pm

I take it back - that's not what it did. It changed the ROOT folder to the one above, making my project folder into this junk:

C:\Documents and Settings\deanc\My Documents\Visual Studio Projects\ExtraMile\iChange\NewHollandImport\Visual Studio Projects\ExtraMile\iChange

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

AND IT JUST DID IT AGAIN!!!!

Post by Dino » Tue Oct 25, 2005 7:55 pm

This is getting to be extremely annoying extremely fast...

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Oct 25, 2005 8:40 pm

Vault doesn't change working folders on its own - it does so in response to Visual Studio requests. Can I assume you are using VS Integration?

If so, what has changed in your Visual Studio setup lately that would want it to change working folders? Did a file or reference get added that is not within your project root?

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Tue Oct 25, 2005 8:42 pm

I reformatted my machine completely, configured Vault and set all my working folders. I think got latest of a solution from Vault, and proceeded to open it, whereby it opened all the contained projects from vault.

I've not even had a chance to change anything yet.

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Oct 25, 2005 8:45 pm

If this was brand new, did you start with an Open From Source Control from withing Visual Studio? If you set working folders manually from the GUI client and then did a Get and then tried to work with IDE integration, the binding will not have been setup correctly, and strange things will happen.

If that is the case, I'd recommend removing the working folders, then doing an Open From Source Control to fresh working folders to see if that helps any.

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Tue Oct 25, 2005 8:45 pm

Can you open a Solution from Vault, or just a project?

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Oct 25, 2005 9:52 pm

You can open either a solution or a project under source control from VS

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

Post by Dino » Tue Oct 25, 2005 11:07 pm

It must be because of the root folder issue - I will just have to suffer it until I can use VS.Net 2005. Tying it this way makes a hurrendous mess of my work.

MS state that it should not be a problem having files outside the root, as long as the source control reports them as "Not Controlled" - is this not how it works?

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed Oct 26, 2005 8:19 am

It is often hard to predict what Visual Studio will do when using the source control interface, so anything is possible. You could test this out by creating a test repository and putting the solution in, and then removing files or projects until it starts working properly, so you'd know what specific file or project it thinks is outside SCC.

Post Reply