Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 03-17-2010, 03:49 AM
DavidNL DavidNL is online now
Registered User
 
Join Date: 09-12-2008
Posts: 6
Question Visual Studio -> Change SourceControl

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\MyAppli cation.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.
Reply With Quote
  #2  
Old 03-17-2010, 06:02 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
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/Ma...laceaction.htm
Reply With Quote
  #3  
Old 03-17-2010, 06:30 AM
DavidNL DavidNL is online now
Registered User
 
Join Date: 09-12-2008
Posts: 6
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
Reply With Quote
  #4  
Old 03-17-2010, 06:38 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
Just replace the part before the comma.
Reply With Quote
  #5  
Old 03-17-2010, 07:13 AM
DavidNL DavidNL is online now
Registered User
 
Join Date: 09-12-2008
Posts: 6
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
Reply With Quote
  #6  
Old 03-17-2010, 07:14 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,034
Oh, I missed that. Then it may not be possible to automate.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 06:15 PM.


Copyright © 1999-2023 Kinook Software, Inc.