Lesson 1: Deploying Web Applications in .NET framework

Printer QR Code in .NET framework Lesson 1: Deploying Web Applications

4. In the Select Item In Project dialog box, select the executable or script. To add an assembly that is part of your current project, select the /bin/ folder, click Add Output, select the project, and then select Primary Output. If you add more than one custom action to a single phase, you can rearrange the cus tom actions by right-clicking them and then clicking Move Up or Move Down.

Storing information in the registry used to be the preferred way of storing application settings. However, the best practice for configuring .NET Framework applications is to store settings in configuration files. There may still be times when you need to add registry entries during setup, however. For example, you might need to configure an aspect of the operating system or another application. To configure a Web Setup Project to add a registry entry during setup, follow these steps: 1. In Solution Explorer, select your setup project. 2. Select the View menu, choose Editor, and then choose Registry. 3. The Registry Settings Editor appears. You cannot browse the computer s full registry structure. Therefore, to add a registry setting in a nested key, you need to add each nested key. For example, to add a setting to HKEY_LOCAL _MACHINE\SOFTWARE\Microsoft\ASP.NET\, you need to add the SOFT WARE, Microsoft, and ASP.NET keys to the HKEY_LOCAL_MACHINE hive in the Registry Settings Editor. 4. Right-click the key you want to add a setting to, select Add, and then select String Value, Environment String Value, Binary Value, or DWORD Value. Type the name of the value, and then press Enter. 5. To define the value, select the registry value, view the Properties window, and set the Value property. To make the installation of the value conditional, define the Condition property. By default, registry keys are not removed when an application is uninstalled. To auto matically remove a registry key, select the key and view the Properties window. Then set the DeleteAtUninstall property to True.

13

You can configure deployment conditions to require specific operating system ver sions, specific service pack levels, and other criteria. Table 13-3 lists commonly used conditions.

Description Version number for Microsoft Windows NT-based oper ating systems, including Microsoft Windows 2000, Windows XP, and Microsoft Windows Server 2003. Version number for early Windows consumer operating systems, including Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Me. Version number of the operating system service pack. Build number of the operating system. Default language identifier for the system. Tool that determines whether the user has administrative privileges. Size of the installed RAM in megabytes. Version of IIS, if installed.

For a detailed list of properties, see the Property Reference in the MSDN Library at http:// msdn.microsoft.com/library/en-us/msi/setup/property_reference.asp.

To evaluate environment variables, preface the variable name with a % symbol, as this example illustrates:

%HOMEDRIVE = "C:" (verify that the home drive is C:\)

To simply check a property for a specific value, you can use the = operator, as the fol lowing example shows:

IISVERSION = "#6" (check for IIS 6.0) VersionNT = 500 (check for Windows 2000)

You can also check for ranges:

IISVERSION >= "#4" (check for IIS 4.0 or later) Version9X <= 490 (check for Windows Me or earlier)

You can also check for multiple conditions using Boolean operators: Not, And (True if both values are True), Or (True if either value is True), Xor (True if exactly one value is True), Eqv (True if both values are the same), and Imp (True if the left term is False or the right term is True). The following example demonstrates these Bool ean operators:

WindowsBuild=2600 AND ServicePackLevel=1 (check for Windows XP with Service Pack 1)