I don't think so. The reason could be different. To my taste, the whole idea of integration of Revision Control System into Visual Studio is not so good. Revision control should act in non-intrusive way and cover all files and directories which should be covered, in a way agnostic to the their nature.
Nevertheless, I want to warn you:
throw out VSS and never ever use it. Not only it is quite obsolete, it's unreliable by design. For example, it is notoriously non-transactional; some concepts are seriously flawed. I know people who suffered dearly from that. Your code asserts are too valuable to trust them to close-source, close in general, unsupportable proprietary tool. Revision control can be free of charge, open-source, supported by big community and much, much lighter and more reliable.
Please see this discussion:
http://www.codeproject.com/Questions/147818/Revision-control-systems-which-to-choose-from.aspx[
^].
See also my past answers:
http://www.codeproject.com/Answers/631391/The-associated-source-control-plug-in-is-not-insta[
^],
http://www.codeproject.com/Answers/302030/How-can-i-structured-to-arrange-source-code-when-i#answer1[
^],
Make an unclickable form[
^].
—SA
Submit an article or tip