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
  • Day 21. Object Role Modeling with Visio
    • Introducing Object Role Modeling
    • Using Visio to Create an ORM Model
    • Adding ORM Facts to the Data Model
    • Creating a Database Diagram from the Conceptual Model
    • Summary
    • Q&A
    • Quiz
    • Exercises
  • Week 3. In Review

Summary

Today you created a new ORM model, used it to create a database diagram, and used the diagram to create a physical database in SQL Server. You learned that by adding facts to the ORM model and setting roles and constraints on those facts, you can easily create a useful conceptual database model. After you've broken down the conceptual process into logical plain-English sentences, you can use Visio and Visual Studio .NET to manage your conceptual data models and physical databases using database diagram projects along with the ORM models that you create. The next step in understanding ORM is to use the tools in Visio to reverse-engineer a good example of a normalized database, such as the Pubs or Northwind databases that ship with MSDE and Visual Studio .NET. Doing so will help you understand how those facts make up the model that in turn creates the database.

Share This