We have a 'custom' file type and we'd like to use the pound sign
(#) to indicate single line comments in the file. I vaguely
recall that a comment indicator could be associated with a file
type in VSS. I've looked all through the help and can't find any
info on it. Am I crazy? Gee, maybe it was PVCS years ago.
Thanks,
- Arnie
Alin Constantin [MSFT] - 28 Mar 2006 10:54 GMT
Hi Arnie,
VSS does not care about # characters in the file's content, so you can
safely use # for comments.
The onnly character I know might matter in the file's content is $, which
can be used for keyword expansion, if the database is configured to allow
this feature http://blogs.msdn.com/korbyp/archive/2003/10/13/54209.aspx

Signature
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.
> We have a 'custom' file type and we'd like to use the pound sign (#) to
> indicate single line comments in the file. I vaguely recall that a
[quoted text clipped - 4 lines]
> Thanks,
> - Arnie
Zane Jarvis - 29 Mar 2006 05:49 GMT
Hi Arnie,
in the ss.ini file place a container as follows
[Keyword Comments]
*.c = "// "
*.cpp = "// "
*.h = "// "
*.inl = "// "
*.asm = "; "
makefile = "# "
<All others> = "* "
Cheers,
Zane
> We have a 'custom' file type and we'd like to use the pound sign (#) to
> indicate single line comments in the file. I vaguely recall that a
[quoted text clipped - 4 lines]
> Thanks,
> - Arnie
Arnie - 29 Mar 2006 17:39 GMT
> Hi Arnie,
>
[quoted text clipped - 11 lines]
> Cheers,
> Zane
Thanks. Yes, I did that but it still doesn't seem to work. I
realize the comments are just so that VSS can add history or
whatever to the file as comments. However, at the moment, the
keywords aren't even being expanded. I'm still looking into it.
BTW, I tried placing the comment definitions in both the
sourcesafe ini file and into ss.ini in my user profile. But as I
said above, without keywork expansion, it doesn't matter very
much.
- Arnie