PDA

View Full Version : Visual Studio -> Change SourceControl


DavidNL
03-17-2010, 03:49 AM
Hi,

After sharing & branching a project with Visualbuild's Sourcesafe action we always need to manually open the branched project in Visual Studio 2008 to execute "File -> Source Control -> Change Sourcecontrol" to make the solution point to the correct (branched) Sourcesafe project.

Can this be automated with Visualbuild somehow?


Example:
1. We share and branche "$\MyApplication" to "$\MyApplication\Released\MyApplicationV1"
2. If i now open "X:\MyApplication\Released\MyApplicationV1\MyApplic ation.sln" its still pointing to the sourcesafe project "$\MyApplication" (which is not correct).
3. So i have to manually go to "File -> Source Control -> Change Sourcecontrol" to point it to "$\MyApplication\Released\MyApplicationV1"

Its step 3 i would like to do with Visualbuild.


Regards,
David.

kinook
03-17-2010, 06:02 AM
I believe the source control binding info is stored in the .sln and project files. You should be able to use the Replace in File action to update that info.
http://www.kinook.com/VisBuildPro/Manual/filereplaceaction.htm

DavidNL
03-17-2010, 06:30 AM
Hi,

I've checked it and you are correct the only file that changes is the solution file.

However i don't understand all of the changes INSIDE this file, so i can not find/replace the values by hand:

SccProjectName0 = \u0022$/MyApplication\u0022,\u0020FAAAAAAA

changed to

SccProjectName0 = \u0022$\MyApplication\Released\MyApplicationV1\u00 22,\u0020VCEAAAAA

u0020VCEAAAAA <--- being the problem

kinook
03-17-2010, 06:38 AM
Just replace the part before the comma.

DavidNL
03-17-2010, 07:13 AM
That would not be correct.

If i replace the part before the comma i don't get the same result because the part after the comma changed from \u0020FAAAAAAA to \u0020VCEAAAAA

kinook
03-17-2010, 07:14 AM
Oh, I missed that. Then it may not be possible to automate.