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

Q&A

1. Is there anything I can't do during a setup using a custom action?

   Not really. Because installation applications take administrative privileges, you have the run of the machine and can do whatever you need to configure the application.

2. Custom actions are going to change my life. Can I have more than one custom action?

   Yes, as a matter of fact, you can have multiple custom actions. You can also have custom actions that occur at different stages of installation or uninstallation. In the Custom Actions Editor, there are four stages of a deployment project's lifetime: install, commit, rollback, and uninstall. Each of these stages can have multiple custom actions. A good example of an uninstall custom action is removing a database that was created during the install. Using the custom dialogs, you can prompt the user for options during install or uninstall, and then base your custom actions on the user's response.

Share This