您使用什么方法将 ASP.Net 应用程序部署到野外? [英] What method do you use to deploy ASP.Net applications to the wild?

查看:16
本文介绍了您使用什么方法将 ASP.Net 应用程序部署到野外?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

目前,我们通过在本地发布网站并将 zip 文件通过电子邮件发送给系统管理员以及(通常)冗长的一组部署说明来部署已编译的 ASP.Net 应用程序.这是因为我们第一次向客户部署 ASP.Net 应用程序时,开发和测试 IIS 实例是相同的,我们无法将站点两次部署到同一台机器上.这为所有后续项目的部署奠定了基调.

Currently we deploy compiled ASP.Net applications by publishing the web site locally and emailing a zip file to the system administrator with a (usually) lengthy set of instructions for deployment. This is because the first time we deployed an ASP.Net application to a customer the dev and test IIS instance were the same, and we were unable to deploy the site twice to the same machine. This set the tone for deployment on all subsequent projects.

我现在正在评估我们的部署方法,并特别关注内置的部署工具;具体来说,我正在研究自定义安装任务并尽可能多地使用标准安装程序功能(主要是用户界面).

I am now evaluating our deployment methods and am looking specifically at the built in deployment tools; specifically I'm looking at custom installation tasks and using as much of the standard installer functionality as I can (mostly the user interface).

其次,我正在考虑合并部署和自动更新.

Secondly, I'm looking at merging deployments and automatic updates.

您如何在组织中部署软件?您使用哪些工具,最常遇到哪些问题?

How do you go about deploying sofware in your organisation? What tools do you use, and what problems do you come across most frequently?

推荐答案

使用复制 Web 工具部署 Web 应用程序
文本来自 Microsoft Training Kit Book Based Development
如果您向许多用户提供 Web 应用程序(例如,允许人们从 Web 下载应用程序并安装它),则 Web 安装项目很有用.如果您负责为您的组织更新特定网站,则每次进行更新时登录到 Web 服务器并安装 Windows Installer 程序包是不切实际的.对于内部应用程序,您可以直接在 Web 服务器上编辑 Web 应用程序.但是,您所做的更改会立即在您的生产 Web 应用程序中实现,这包括可能存在的任何错误.为了让自己能够测试 Web 应用程序,您可以在计算机上编辑 Web 应用程序的本地副本,并使用 Copy Web 工具将更改发布到生产 Web 服务器.您还可以使用 Copy Web 工具将更改从临时服务器发布到生产 Web 服务器,或在任意两个 Web 服务器之间发布.复制 Web 工具可以将单个文件或整个网站复制到源网站和远程网站或从源网站和远程网站复制.您还可以选择同步文件,这涉及仅复制更改的文件并检测可能的版本冲突,其中源站点和远程站点上的同一文件已被单独编辑.Copy Web 工具无法合并单个文件中的更改;只能复制完整的文件.

Deploy Web Applications Using the Copy Web Tool
Text from Microsoft Training Kit Book Web Based Development
Web Setup Projects are useful if you are providing a Web application to many users (for example, allowing people to download the application from the Web and install it). If you are responsible for updating a specific Web site for your organization, it’s impractical to log on to the Web server and install a Windows Installer package each time you make an update. For internal applications, you can edit the Web application directly on the Web server. However, changes you make are immediately implemented in your production Web application, and this includes any bugs that might be there. To enable yourself to test a Web application, you can edit a local copy of the Web application on your computer and publish changes to the production Web server using the Copy Web tool. You can also use the Copy Web tool to publish changes from a staging server to a production Web server, or between any two Web servers. The Copy Web tool can copy individual files or an entire Web site to or from a source Web site and a remote Web site. You can also choose to synchronize files, which involves copying only changed files and detecting possible versioning conflicts in which the same file on both the source and remote site have been separately edited. The Copy Web tool cannot merge changes within a single file; only complete files can be copied.

这篇关于您使用什么方法将 ASP.Net 应用程序部署到野外?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆