<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Gaute's .net weblog - Source Safe</title>
    <link>http://gaute.amende.no/</link>
    <description>thoughts on programming and computer related stuff</description>
    <language>en-us</language>
    <copyright>gaute</copyright>
    <lastBuildDate>Sun, 10 Aug 2008 16:22:26 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>gaute@amende.no</managingEditor>
    <webMaster>gaute@amende.no</webMaster>
    <item>
      <trackback:ping>http://gaute.amende.no/Trackback.aspx?guid=8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7</trackback:ping>
      <pingback:server>http://gaute.amende.no/pingback.aspx</pingback:server>
      <pingback:target>http://gaute.amende.no/PermaLink,guid,8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7.aspx</pingback:target>
      <dc:creator>Gaute Magnussen</dc:creator>
      <wfw:comment>http://gaute.amende.no/CommentView,guid,8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7.aspx</wfw:comment>
      <wfw:commentRss>http://gaute.amende.no/SyndicationService.asmx/GetEntryCommentsRss?guid=8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">I am one of those who still from time to
time get to use MS SourceSafe. This week I had a problem with some production code.
To make a long story short, I had to rollback the code to see if our code was the
source of the problem. However no labels or anything was made.<br /><br />
That's when I found out that using the sourcesafe command line tool, one could get
the source as it was on a specific date. Here's how it's done:<br /><br />
First you need to set the an environmental variable named SSDIR to the location of
the sourcesafe database. In Windows Vista, this is done by selecting properties on
my computer, selecting Advanced System Settings, and the selecting Environmental Variables
on the Advanced tab.<br /><br />
Second you have to open a command prompt and locate the SS.exe file which should be
located in the sourcesafe-folder. I then created a new folder for where I wanted my
new files and then I wrote something like: "c:\program files\source safe\win32\ss
get $/Project/location to . -vd30/04/2007 -R"<br /><br />
I believe the date format changes depending on the country selected in your system
settings.<br /><br />
This trick did magic and I was able to find out that our code was not the source of
the problems experienced in the production environment.<p></p><img width="0" height="0" src="http://gaute.amende.no/aggbug.ashx?id=8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7" /></body>
      <title>Get Sourcesafe data from a specific date.</title>
      <guid isPermaLink="false">http://gaute.amende.no/PermaLink,guid,8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7.aspx</guid>
      <link>http://gaute.amende.no/GetSourcesafeDataFromASpecificDate.aspx</link>
      <pubDate>Sun, 10 Aug 2008 16:22:26 GMT</pubDate>
      <description>I am one of those who still from time to time get to use MS SourceSafe.
This week I had a problem with some production code. To make a long
story short, I had to rollback the code to see if our code was the
source of the problem. However no labels or anything was made.&lt;br&gt;
&lt;br&gt;
That's when I found out that using the sourcesafe command line tool, one could get
the source as it was on a specific date. Here's how it's done:&lt;br&gt;
&lt;br&gt;
First you need to set the an environmental variable named SSDIR to the location of
the sourcesafe database. In Windows Vista, this is done by selecting properties on
my computer, selecting Advanced System Settings, and the selecting Environmental Variables
on the Advanced tab.&lt;br&gt;
&lt;br&gt;
Second you have to open a command prompt and locate the SS.exe file which should be
located in the sourcesafe-folder. I then created a new folder for where I wanted my
new files and then I wrote something like: "c:\program files\source safe\win32\ss
get $/Project/location to . -vd30/04/2007 -R"&lt;br&gt;
&lt;br&gt;
I believe the date format changes depending on the country selected in your system
settings.&lt;br&gt;
&lt;br&gt;
This trick did magic and I was able to find out that our code was not the source of
the problems experienced in the production environment.&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://gaute.amende.no/aggbug.ashx?id=8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7" /&gt;</description>
      <comments>http://gaute.amende.no/CommentView,guid,8eb0a7a5-fe8c-45db-95a7-37e4ae5fd4d7.aspx</comments>
      <category>.NET</category>
      <category>Source Safe</category>
    </item>
  </channel>
</rss>