Raghvendra Shukla,
Cutting clear of the bullshit replies before me, here's a real answer.
In Visual Studio.NET you can bind or unbind your projects to VSS using a
menu item under VSS. To initially configure them to use with VSS, just drag
drop them into VSS while checking the "recursive" option.
Now for the practicality part of it all. Sourcesafe uses as it's DB access
technology a much loved/hated Microsoft technology called "jet". Jet while
is perfect for 5ish user scenarios, is not ideal for large scale projects.
It does have it's advantages though, but that is another discussion. If you
want something for free (included in your MSDN universal .... otherwise
around $499), Visual Sourcesafe is a good choice. But if you are running an
Enterprise level project, with 20-200 developers, you might want to look
elsewhere. My personal favorites are Rational, PVCS, and what I like the
best Borland Starteam.
Might I add, Microsoft doesn't use VSS for it's own largescale projects
because S.Safe is just not the right tool for that. But MS isn't ignoring
S.Safe anymore, with Vstudio 2005, you are gonna have a fairly reworked
s.safe with web access etc. but it's target market is still small projects
(as far as I know).
S.safe isn't necessarily a bad tool, it's simple and ideal for a small
project. All other alternatives I mentioned above are ridiculously expensive
in comparison.
- Sahil Malik
Independent Consultant
You can reach me thru my blog at -
http://www.dotnetjunkies.com/weblog/sahilmalik/