<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Visual Source Safe 2005 and uVision 4</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/26786/visual-source-safe-2005-and-uvision-4</link><description> 
Hi all, 

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

 
I&amp;#39;ve chosen the &amp;#39;&amp;#39; Microsoft Visual SourceSafe6.SVCS &amp;#39;&amp;#39;
template file and edited command lines to reflect</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Visual Source Safe 2005 and uVision 4</title><link>https://community.arm.com/thread/102282?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 06:16:45 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:06764ca7-50ab-4627-9a5d-f179670cc409</guid><dc:creator>M D</dc:creator><description>&lt;p&gt;&lt;p&gt;
Yes but... I dit also the following test:&lt;/p&gt;

&lt;p&gt;
- issue a SS command with uVision: nothing happen&lt;br /&gt;
- go to the &amp;#39;&amp;#39;Build Output&amp;#39;&amp;#39; window and copy the command log-line&lt;br /&gt;
- open a command shell, set SSDIR=V:\&lt;br /&gt;
- paste the command log-line to the shell and press enter&lt;br /&gt;
- IT WORKS!&lt;/p&gt;

&lt;p&gt;
So, if the log is not different from what uVision really does, i
can&amp;#39;t understand why is not working.&lt;/p&gt;

&lt;p&gt;
The quotes in the command log-line are correctly placed to manage
spaces in pathnames.&lt;/p&gt;

&lt;p&gt;
I am confused&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Visual Source Safe 2005 and uVision 4</title><link>https://community.arm.com/thread/90619?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 05:34:20 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d8c3ceb7-8cb5-4d2e-92f7-35ed3455bf31</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
The last time I played with this kind of stuff (admitedly, a long
time ago), uVision really didn&amp;#39;t cope well with spaces anywhere in
any path - including the path to the executable...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Visual Source Safe 2005 and uVision 4</title><link>https://community.arm.com/thread/58646?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 05:14:06 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:662b29eb-0efb-4ce0-8dfe-30eb090a273d</guid><dc:creator>M D</dc:creator><description>&lt;p&gt;&lt;p&gt;
Little but important update:&lt;/p&gt;

&lt;p&gt;
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!&lt;/p&gt;

&lt;p&gt;
So, IMHO, the problem seems related to how uVision issues those
commands...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>