Jan Schreuder on .Net

.Net code samples, experiences, observations

View my professional profile on LinkedIn

Recent Posts

Tags

News

  • Inappropriate comments will be deleted at my discretion.

    The information and code samples in this weblog is provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to the merchantability and/or fitness for a particular purpose.

Community

Email Notifications

Tool suppliers

Tools

General

Microsoft

Favorite blogs

Archives

Fixing a problem with History view in VSS 2005

One would think that Microsoft has improved Visual Source Safe a lot with the release of VSS 2005. And until this week I was happy to say that it appeared to be much more stable and reliable than any of the previous versions. But today I tried to view the difference between two checked-in versions of a stored procedure.

I right clicked the file in VSS and selected "Show History". I clicked OK in the dialog that VSS presented to me and nothing happened. I thought my installation was somehow corrupted. Why, I honestly don't know, but I proceeded in re-installing VSS 2005. But that didn't solve my problem. So I went to the Microsoft Visual Studio Source Control and Sourcesafe forum and found this thread which contains the following solution to the problem:

  1. Start Visual SourceSafe Administrator.
  2. On the Tools menu, click Options.
  3. In the Options dialog box, click the Time Zone tab.
  4. Change the Time Zone setting for the database to <None Specified>. This setting is the first entry in the list.
  5. Click OK, and then quit Visual SourceSafe Administrator.
  6. If you have Visual SourceSafe Explorer (SSEXP) open, close and then reopen SSEXP to apply the changes

And then the history option works again. Weird right?

Comments

steampunk said:

Just out of curiosity, do you think this has anything to do with the Time Zone update (http://support.microsoft.com/kb/928388) earlier this year?  My company switched to TFS before the time zone changes went into effect, but I've never run into that problem in the 14+ months I had  been using VSS 2005.  

You would think it wouldn't be a problem, but you never know.

# April 5, 2007 2:30 PM

Jan Schreuder said:

I really wouldn't know. It did annoy me though.

# April 5, 2007 11:29 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Please add 3 and 6 and type the answer here: