Block CS.Net from changing working folders
Moderator: SourceGear
Block CS.Net from changing working folders
Can you add an option to block VS.Net from changing the working folders in Vault? This has happened a few times, and I have to keep resetting them - I really do know what the true working folders are, and I do not want VS.Net sticking it's nose in any more - can you add an option to block updates from VS.Net?
This wouldn't be advisable, because VS determines where the working folders should be, and trying to change them in SC won't change them in VS, and everything will be very messed up.
You could always try to reset things by doing a new Open From Source Control, which when VS is supposed to set the working folder.
Also, if you can identify what action in VS causes the working folder to get changed, let us know, so we check it out here and see if Vault is involved at all.
You could always try to reset things by doing a new Open From Source Control, which when VS is supposed to set the working folder.
Also, if you can identify what action in VS causes the working folder to get changed, let us know, so we check it out here and see if Vault is involved at all.
I can't use the Open from source because of linked files, and VS.Net will just trash my paths. In Vault I have this:
Visual Studio Projects\Client\Solution\Project
Some files are linked from paths in the Visual Studio Projects folder (as they are common to every single project I write) so Visual studio does something like this:
Visual Studio Projects\Client\Solution\Project\Visual Studio Projects\Common Files\File
That is absolutely not what I want, and is completely wrong. Trust me - I do know better than VS.Net where my files are and what the working folders are.
One of the reasons for linked files is a code generator, and some of my projects have in excess of 150 files linked, and I have about 100 projects so making them shared files is not an option now. Short of re-writing the code generator to generate the files into the project folder rather than a standard place like they do now, I cannot see how I can avoid linked files that are outside the root, but these linked files really cause a lot of problems when really they shouldn't.
Visual Studio Projects\Client\Solution\Project
Some files are linked from paths in the Visual Studio Projects folder (as they are common to every single project I write) so Visual studio does something like this:
Visual Studio Projects\Client\Solution\Project\Visual Studio Projects\Common Files\File
That is absolutely not what I want, and is completely wrong. Trust me - I do know better than VS.Net where my files are and what the working folders are.
One of the reasons for linked files is a code generator, and some of my projects have in excess of 150 files linked, and I have about 100 projects so making them shared files is not an option now. Short of re-writing the code generator to generate the files into the project folder rather than a standard place like they do now, I cannot see how I can avoid linked files that are outside the root, but these linked files really cause a lot of problems when really they shouldn't.
I understand your frustration, but the "all files must be under a common root" problem is just how Visual Studio works. You might want to get on the MS forums for VS and see if they have plans to relax that in the future, or if there are other workarounds other than sharing the files within source control
According to Microsoft, they don't have to be under a common root, you just need to report them as "not controled":
http://support.microsoft.com/?kbid=896702
http://support.microsoft.com/?kbid=896702