Random change of working folder
Moderator: SourceGear
Random change of working folder
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
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
AND IT JUST DID IT AGAIN!!!!
This is getting to be extremely annoying extremely fast...
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?
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?
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.
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.
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?
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?
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.