| Q1: | You didn't discuss working on ASP.NET applications. Why not? |
| A1: | The SourceSafe process is the same for any type of application. The same capabilities you learned about today using a Windows Forms application work with ASP.NET applications, deployment projects, and add-in projectsbasically all project types available in .NET are capable of being stored in SourceSafe. |
| Q2: | I have deleted a file in my solution, but when I go back to the SourceSafe Explorer, it keeps showing back up. What am I doing wrong? |
| A2: | You aren't doing anything wrong; you just skipped a step. Any time you delete a file from the Visual Studio .NET IDE, you must go to the SourceSafe Explorer and delete the file from there also. |
| Q3: | I'm using Visual Studio .NET, but not the Architect version. Can I buy SourceSafe separately? |
| A3: | Yes. SourceSafe is a regular retail product from Microsoft and can be purchased from shop.microsoft.com or any software reseller. |
| Q4: | I like the Visual Studio .NET integration, but I actually need to manage SourceSafe from the SourceSafe Administrator and the SourceSafe Explorer. Can I get information about this stuff online? |
| A4: | There are two good places to learn more about SourceSafe. The first is the .NET Framework SDK. Do a search for Source Control, and you'll find some documentation. In addition, there's an Architect Developer center on MSDN that has an article series about SourceSafe. The link is http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbdal/tdlg_rm.asp |