• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 873 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Visual Source Safe 2005 and uVision 4

M D

Hi all,

I'm trying to make uVision 4.03q to work with Microsoft Visual SourceSafe 2005 (can't find any older VSS6 CD at the moment...)

I've chosen the ''Microsoft Visual SourceSafe6.SVCS'' template file and edited command lines to reflect my installation.

Basically, the executables are:

C:\Programmi\Microsoft Visual SourceSafe\ssexp.exe

and

''C:\Programmi\Microsoft Visual SourceSafe\ss.exe''

Ths VSS database is on a server, and the drive is mapped as V: on my PC (XP Pro SP3), so the database field is set to

''V:\srcsafe.ini''

The Source safe explorer is launched and works fine.

All other commands required the SSDIR variable so I added to them all:

''SSDIR=V:\''

I tried many different commands (set current, create, checkin...), but none of them seems to have any effect on the database.

Even if I ask to checkout a file that is currently in uVision project but has never been checked-in in VSS, uVision-VSS doesn't show any error.

All commands simply seems to fail gracefully :-)

I checked the syntax of some commands against the help of VSS and they seems to be correct (off course not all possible commands are implemented, nor all possible options are used in commands...)

Anyone out there succeeded in this ?

Also, is there any procedure to follow when using uVision and VSS (in particular for creating new projects?)
Any doc I should read?

Best regards

Marco

Parents
  • 0

    Little but important update:

    if I open a prompt shell, set the SSDIR to V:\ and type in a command as specified in the script file (for example create project) IT WORKS, I can see the changes with SSExplore!

    So, IMHO, the problem seems related to how uVision issues those commands...

Reply
  • 0

    Little but important update:

    if I open a prompt shell, set the SSDIR to V:\ and type in a command as specified in the script file (for example create project) IT WORKS, I can see the changes with SSExplore!

    So, IMHO, the problem seems related to how uVision issues those commands...

Children
  • 0 in reply to M D

    The last time I played with this kind of stuff (admitedly, a long time ago), uVision really didn't cope well with spaces anywhere in any path - including the path to the executable...

  • 0 in reply to Andy Neil

    Yes but... I dit also the following test:

    - issue a SS command with uVision: nothing happen
    - go to the ''Build Output'' window and copy the command log-line
    - open a command shell, set SSDIR=V:\
    - paste the command log-line to the shell and press enter
    - IT WORKS!

    So, if the log is not different from what uVision really does, i can't understand why is not working.

    The quotes in the command log-line are correctly placed to manage spaces in pathnames.

    I am confused