I'm doing some tests with the "VSS Share File(s)" action. It seems to work ok until i come to the "Get Options". Here i fill in the "Working Folder" and i check the option "Force directories". The other options stay their default value. Now what i would expect when i run this action is that when the branch is done, yes i have "Branch after sharing" checked, that a get latest will be done on the files in the new branched project.
Unfortunatly this is not the case. Did i missinterpet the option or does it do a get latest on the files before it is going to branching them.
The help isn't that helpful either, it shows the screen but it doesn't explain the options in the screen.
Thanks for posting. Sorry to hear you’re having problems.
The VSS Share Files(s) action uses the SourceSafe share command to create the share. It’s possible this command is being called with the wrong parameters.
To check, select your VSS Share File(s) action and then click on the Action Inspector tab in the FinalBuilder IDE. Near the top there is a section called “Debugging” and a checkbox called “Extra Debug Output”. If you check this box and run the action again, you should see the command line shown in the build log for the action. Could you copy this and post it to the forum, please?
I hope it is usefull. We are using Visual SourceSafe Version 6.0 (Build 8163), i don’t know if it is usefull to know this.
I did some checking in the helpfile from SourceSafe and saw that the -G is for the get. Maybe thats the problem because the debug info says -GF- at the end.
One other question to you. You told me to check the “Extra Debug Output” checkbox to get extra debug info. Is there any other place where i can set this option on a global level. I ask this because when uncheck it the debug info is also visible in FinalBuilder.
Thanks for this. You’re probably right that the -GF- is to blame, that’s actually disabling the Force Directories option (which tells VSS to use the current directory not the project working directory, to do the Get.) This is a bug in FB.
I’ve fixed the bug so the Force Directories option is passed appropriately, we should have a test build available soon.
Regards,
Angus
PS With regards to Extra Debug Output, what version of FB are you using?
There still is no getlatest done. I tried setting the working folder to anohter folder but that didn't work either.
Regarding the Extra Debug Output i was using version 5.5.0.348. And in version 5.5.0.412 i didn't check this option and still got the output you see above.
Could you explain exactly what project you’re trying to share where? The VSS Share command is a fairly confusing entity, and I want to make sure we’re on the same page.
The project that i’m going to share is $/Elpado/Current and i’m sharing to $/Elpado/Releases/Version_x.x.x.x
The options are set like: Source Project: $/Elpado/Current Source File(s): New project name: %BranchVersionText%, which says “Version_x.x.x.x” Destination project: $/Elpado/Releases Branch after sharing: checked Recursive: checked Specific Version: Answer Yes to Input prompts: checked Comment: Do not GET files: unchecked Force Directories: checked Working Folder: C:\Projects\Elpado\Releases Make retrieved copy writeable: unchecked
In VSS is the working folder that is set on $ C:\Projects
That is all the information that i can think of that is relevant. If you need some more information please let me know.
If you set the working folder to the destination directory for the shared project (ie C:\Projects\Elpado\Releases\Version_x.x.x) does it work as expected?
I tried your sugestion. The result of this action was that under the folder Releases the folder Version_x.x.x.x was made but there where no files to be found
Looks a bit like it does the get but not the recursive bit.
It is good to see that there are still companies that do their best to help the customer. Thanks foor the help and when you have a new version to test then please let me know. Ofcourse the workaround that you suggested is something that i thought of too. Our first idea was to do a checkout of all the files in our project, that would do the get for me. But we are not going on that road so i will put a get action in my chain.