0

We are actively using the FogBugz integration with Microsoft Visual SourceSafe (VSS). Yes I know, not Kiln. :-(

It took some time to get it working, primarily because of an x64 issue. And we had to change vss_fbupdate.wsf, because deleted files caused it to fail importing the journal.

Now that it works, I like the functionality very much. However, I wonder if it would be possible to improve the experience a bit. Some suggestions:

  • use the diff -d argument to try harder to find few differences

  • preserve multiple consecutive spaces in source code (use <pre> or &nbsp; or whatever)

  • color keywords like in [code] blocks

I can understand if VSS integration is considered obsolete...

flag
1 
Many would consider VSS to have been obsolete the day it came out. Manual file versioning is almost better than VSS :-) – cdeszaq Nov 30 2010 at 14:15

2 Answers

1

Well, it is a bit of an antique, but most of those suggestions could enhance the other non-Kiln integrations we do. Thanks for the suggestions!

If anyone likes this idea for VSS or anything else, go ahead and upvote the question (not this answer!) and we'll look into it!

link|flag
0

To preserve whitespace in the Differences, one can use the BugMonkey plugin along with a customization like this:

name:          Whitespace in VSS differences
description:   Preserve whitespace in Visual SourceSafe file differences
author:        Michel de Ruiter
version:       1.0.0.0

css:

table.fileDiff td { white-space: pre; }
link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.