Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

Chapter 1. Introduction > Where to Deploy the .NET Framework - Pg. 12

12 Deploying .NET Applications Lifecycle Guide Scripted or Hosted Applications Scripted or hosted applications use existing hosting features of an operating system or application to run, meaning that the code can be interpreted at run time and does not have to be precompiled. The most common examples are Visual Basic Scripting Host (*.vbs) and Windows Scripting Host (*.wsf) applications. While these types of applications performs specific functions, the commonly do not have much if any user interface. These types of applications can often be incorporated into other applications to perform specific functions. Where to Deploy the .NET Framework The .NET Framework needs to be deployed on all computers that will run managed code. If you have a distributed application, however, you will not necessarily need to deploy the Framework on all participating computers. Which computers require the Framework will typically depend on the role which they fill. This section will help you determine where it is appropriate to deploy the Framework. Clients Whether you need to deploy the Framework on your client base or not will depend in part on the type of .NET-based applications you are deploying. If you are deploy- ing (or plan to deploy) Windows Forms applications, you need to ensure that the Framework is installed, or they will not operate properly. This is because .NET Framework classes are responsible for the GUI of the application. For ASP.NET applications, in many cases the client will not need the Framework installed. This is because the .NET Framework is being used at the server to generate the user interface and the server supplies the client with standard HTML. However, if your ASP.NET application uses Windows Forms user controls, your clients will need the Framework installed. This is because Windows Forms user controls rely on the .NET Framework to manage their execution. Note: Using Windows Forms user controls introduces a number of other issues, such as browser and code security, with which you need to be familiar. A full discussion is outside the scope of this guide. For more information, see "Writing Secure Managed Controls" on MSDN. Web Servers If you use server-side code in your .NET-based applications, then you must ensure that the target Web servers for your solution have the .NET Framework installed, or your application will not function properly. The distributed nature of modern