Sams Teach Yourself .Net in 21 Days

By Jason Beres

• 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

Summary

Today you learned how to use Visual SourceSafe and its tools in the Visual Studio .NET IDE. By putting your projects under source control, you have the benefit of knowing your source code is safe from accidental deletion of files and in a durable data store that can be backed up for archive purposes. By diligently checking in files after you've worked with them, you can build up a version history of your application's files. This enables you to roll back changes or even complete installations of applications with a few clicks of the mouse. In a team development environment, SourceSafe should be a requirement. If you're a single developer working alone on projects, you should always use SourceSafe to keep track of changes made to your code.

You've just about completed all 21 days of learning Visual Studio .NET. Tomorrow, on Day 21, you learn how to implement object role modeling using Visio.

Share This