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
    • Introduction to ASP.NET Deployment
    • Creating an ASP.NET Application for Deployment
    • Deploying ASP.NET Applications Using Copy Project
    • Deploying ASP.NET Applications Using Copy
    • Deploying ASP.NET Applications with Windows Installer
    • Summary
    • Q&A
    • Quiz
    • Exercises
  • 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
  • Week 3. In Review

Introduction to ASP.NET Deployment

Like Windows Forms applications, the solution for an ASP.NET application contains all the information about the project that the installation package needs. Because of this, you can use simple methods (such as XCopy) or more robust methods (such as Windows Installer) to deploy an application. The decisions you need to make when determining how to deploy your applications to a Web server are

• Does the application already exist on the Web server?
• Do special Registry entries need to be made for COM components when I deploy?
• Do I need to worry about other files that aren't part of my application?

Based on the answers to these questions, your options for deploying an ASP.NET application can vary. The key ingredient to making an ASP.NET application function is Internet Information Server (IIS). IIS is the Web server that serves up Web pages, and it's what the ASP.NET runtime uses to make your ASP.NET applications work.

If you're deploying a Web project for the first time, you can use three methods of deployment:

• Copy Project— This copies the necessary files to a new directory on the Web server. It doesn't configure the Web server.
• XCopy Deployment— This simply uses the DOS XCopy command to copy a file from point A on your development machine to point B on the Web server. You must manually configure the directory and application on IIS to make the Web site accessible.
• Windows Installer— This creates and configures the ASP.NET application on a Web server. Using Windows Installer is the most full-featured and robust way to deploy ASP.NET applications.

You are going to learn how to use each of these methods of deployment.

Share This