Sams Teach Yourself .Net in 21 Days
- Table of Contents
- Copyright
- About the Author
- About the Technical Editor
- Acknowledgments
- We Want to Hear from You
- Introduction
- Week 1: At a Glance
- Day 1. Introduction to the Microsoft .NET Framework
- Day 2. Introduction to Visual Studio .NET
- Day 3. Writing Windows Forms Applications
- Day 4. Deploying Windows Forms Applications
- Day 5. Writing ASP.NET Applications
- Day 6. Deploying ASP.NET Applications
- Day 7. Exceptions, Debugging, and Tracing
- Week 1. In Review
- Week 2: At a Glance
- Day 8. Core Language Concepts in Visual Basic .NET and C#
- Day 9. Using Namespaces in .NET
- Day 10. Accessing Data with ADO.NET
- Day 11. Understanding Visual Database Tools
- Day 12. Accessing XML in .NET
- Day 13. XML Web Services in .NET
- Day 14. Components and .NET
- Week 2. In Review
- Week 3: At a Glance
- Day 15. Writing International Applications
- Day 16. Using Macros in Visual Studio .NET
- Day 17. Automating Visual Studio .NET
- Day 18. Using Crystal Reports
- Day 19. Understanding Microsoft Application Center Test
- Day 20. Using Visual SourceSafe
- Introducing Visual SourceSafe
- Installing VSS
- Using the Visual SourceSafe Administrator
- Using the Visual SourceSafe Explorer
- Creating Your First VSS Project
- Using the Integrated SourceSafe Tools in Visual Studio .NET
- Viewing the History of a File in SourceSafe
- Opening an Existing SourceSafe Project
- Adding New Project Items or Projects
- Renaming Projects or Project Items
- Summary
- Q&A
- Quiz
- Exercises
- Day 21. Object Role Modeling with Visio
- Week 3. In Review
Q&A
-
You didn't discuss working on ASP.NET applications. Why not?
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 projects—basically all project types available in .NET are capable of being stored in SourceSafe.
-
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?
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.
-
I'm using Visual Studio .NET, but not the Architect version. Can I buy SourceSafe separately?
Yes. SourceSafe is a regular retail product from Microsoft and can be purchased from shop.microsoft.com or any software reseller.
-
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?
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/dnbda/html/tdlg_rm.asp
Quiz | Next Section

Account Sign In
View your cart