.NET应用部署生命周期指南

需积分: 9 49 浏览量更新于2024-07-31 收藏 949KB PDF 举报

"Deploying .NET Application LifeCycle Guides" 这篇文档是关于.NET应用程序部署生命周期的指南，主要关注从开发计算机到测试环境的应用程序部署过程。此外，它还提供了在发布流程中将应用部署到预生产（阶段）服务器的建议。这份指南由微软公司发布，反映了截至发布日期时微软对相关议题的最新观点。由于市场条件的变化，微软无法将其视为对未来的承诺，并且不能保证在发布日期之后提供的信息准确性。文档的内容旨在提供信息，不包含任何明示或默示的保证。用户应遵守所有适用的版权法律，未经微软公司明确书面许可，不得复制、存储此文档的任何部分，或以任何形式（电子、机械、影印、录音或其他方式）传播，或用于任何目的。该文档作为微软Visual Studio .NET、Visual Basic .NET、Visual C++、Visual C#、Visual J#.NET以及/或微软其他开发工具的配套资料，帮助开发者和团队理解并执行整个.NET应用程序的生命周期管理。文档可能涵盖以下关键知识点： 1. **开发环境设置**：介绍如何配置开发计算机以支持.NET应用程序的开发，包括安装必要的SDK、IDE和其他工具。 2. **版本控制**：强调版本控制的重要性，推荐使用Git、SVN等工具，以确保代码的版本管理和协作开发。 3. **单元测试与集成测试**：讨论如何编写和执行测试用例，确保代码质量并在不同阶段捕获潜在问题。 4. **持续集成与持续部署(CI/CD)**：介绍如何建立自动化构建和部署流程，以实现从代码提交到测试环境的快速反馈循环。 5. **测试环境**：详细说明如何设置和管理测试环境，以便模拟真实世界的使用情况，对应用程序进行全面测试。 6. **预生产环境**：讨论在发布前将应用程序部署到预生产服务器的策略，以验证代码在接近生产环境中的表现。 7. **发布流程**：描述如何准备和执行发布过程，包括代码打包、版本控制、发布审批和错误处理机制。 8. **监控与日志记录**：建议如何收集和分析应用程序运行时的数据，以便识别性能瓶颈和故障。 9. **回滚策略**：解释在遇到问题时如何回滚到之前的版本，以保持系统的稳定运行。 10. **安全性和合规性**：强调在部署过程中遵循的安全最佳实践，如代码审查、数据加密和合规性检查。通过遵循这份.NET应用程序部署生命周期指南，开发团队能够更有效地管理他们的软件项目，确保从开发到发布的每个步骤都得到有效控制，从而提高产品质量和用户满意度。

Deploying .NET Applications Lifecycle Guide10

●

Extensible Markup Language (XML) Web services

●

Windows Services

●

Console applications

●

Scripted or hosted applications

We will discuss each of these in turn:

Windows Forms Smart Client Applications

In Windows Forms Smart Client applications, the logic and code used to build the

GUI runs on the client computer. Windows Forms controls and menus are actually

.NET Framework classes, as are the Windows Forms themselves. In addition, dis-

play effects, such as colors, borders, sizes, and positions are all controlled by access-

ing classes and enumerations from the .NET Framework class library.

Windows Forms Smart Client applications provide the following benefits:

●

A rich user interface

●

Full access to the local disk and local application programming interfaces (APIs)

●

Elimination of network latency (since the application runs on the client machine)

●

Multiple deployment options

●

Off-line application support

●

Offloading of processing to the client machine

●

Ability to interact with other locally installed applications

ASP.NET Applications (Web-based Applications)

Much of the logic and code used to build the user interface for a Microsoft ASP.NET

application resides (and runs) on a Web server, rather than on the computer at which

the user is sitting. The browser-based GUI is dynamically built by your ASP.NET

application, which transmits HTML to the browser. The GUI may be supplemented

with some client-side script to provide ease of usability, increased responsiveness,

data-entry validation, and dynamic display effects, but the bulk of the interface is

controlled by server-based code to which the client Web browser does not have

direct access. In effect, the client uses HTML, supplemented by dynamic HTML

(DHTML), to present the user interface. Although the server-side code depends on

the .NET Framework to build the GUI, it produces browser-agnostic HTML.

ASP.NET applications may also include Windows Forms user controls. These are

assemblies referenced from Web pages that are downloaded to the user’s computer

and executed upon demand. These controls can provide extra functionality to your

application, much like Microsoft ActiveX® controls hosted in a Web browser did in

the past.

Deploying .NET Applications Lifecycle Guide12

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

Chapter 1: Introduction 13

Internet or intranet-based applications means that Web servers often perform a

number of different roles in your .NET applications. You might use Web servers

to provide any (or all) of the following features for your distributed Framework

application:

●

ASP.NET Web Forms for the GUI

●

Web Services for reusable, Web-based functionality

●

Transfer of XML or text-based data

●

Intermediate XML or text-based processing

●

Connectivity and communication across computer and network boundaries

Business Logic Servers

In some distributed Framework applications, there will be separate computers used

to encapsulate business logic. The advantages of doing so include ease of manage-

ability and scalability, among others. In a pure .NET environment, this business logic

will be provided by .NET components and so the Framework will be required.

However, in some cases your .NET-based application may be replacing a legacy

application where all the business logic was encapsulated in COM objects. .NET-

based applications can interoperate with COM objects, so in this circumstance you

could leave any servers that exclusively run the Business Logic tier unchanged and

not install the .NET Framework on those computers. However, in the medium term

you should consider updating the components to take advantage of the .NET

Framework.

.NET Framework to Database Servers

For scalability, manageability, stability, and fault-tolerance, data tiers, in distributed

applications, are often physically separated from the other tiers in a typical solution.

Microsoft SQL Server™ 2000 does not require the .NET Framework to be installed.

Therefore, if your application architecture does include a physically separate Data

tier, .NET Framework does not need to be installed on your database servers and

analysis servers. However, if you need .NET assemblies to execute on your database

servers, the .NET Framework does need to be installed on those computers.

Deploying the .NET Framework

After determining which computers participate in your distributed .NET-based

application require the .NET Framework, you need to ensure that the Framework is

installed correctly on the appropriate computers in your production environment.

剩余165页未读，继续阅读

ouershuo

粉丝: 1
资源: 1

.NET应用部署生命周期指南

记一次Tomcat卡死在 Deploying web application 步骤的问题.doc

信息: Deploying web application directory lx01

Deploying .NET Applications Lifecycle Guide

Deploying an application using Docker and Kubernetes

Deploying Cisco Wide Area Application Services 2nd Edition

ASP.NET微软官方培训视频(En) 10-Configuring Building and Deploying your Web Application

deploying web application dire

error deploying web application archive

org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory

org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory

最新资源