C＃.NET - 部署＆QUOT;非常＆QUOT;自定义应用程序 [英] C# .Net - deployment "very" custom application

问题描述

我们正在部署的非常的自定义应用程序。

We are working on deploying a very custom application.

该应用程序是主程序（也是唯一的程序），将运行在PC上，但它取决于必须通过单独的安装程序中安装了多个第三方安装程序。其中有些是标准的MSI，安装防护罩，其他过时的设置等。

The application is the main program (and only program) that will run on the PC, but it depends on multiple 3rd party installers that must be installed via separate setup programs. Some of these are standard MSI, install shield, other outdated setups, etc.

在最重要的是，我们必须部署SQL Server的防爆preSS 2005年，安装IIS如果未发现设置了一个网站。

On top of that we must deploy SQL Server Express 2005, install IIS if it is not found and setup a website.

我们的最终终端用户部署，这将是一个人的技术经验，在新的开箱即用的PC XP SP3。

Our final end user deploying this will be a person with technical experience on a new "out of the box" PC with XP SP3.

什么是一个好的选择发展呢？维克斯？ Visual Studio安装项目可能不会削减它。还有一种莫名其妙运行的其他微星的同时，微星已经运行的问题。

What is a good option for developing this? WiX? Visual Studio setup projects may not cut it. There is also the issue of somehow running other MSI's while an MSI is already running.

它会发挥更好的作用作为一个标准的C＃应用​​程序，需要.NET为preinstalled？然后，它只会提示输入几个选项​​再运行几个安装程序，我想。

Would it function better as a standard C# application that requires .Net to be preinstalled? Then it would merely prompt for a few options then run several installers I suppose.

有什么想法？我们想preFER坚持到C＃.NET。

Any thoughts? We'd prefer to stick to C# .Net.

推荐答案

不XP SP3已经安装了.NET运行库？

Doesn't XP SP3 already have a .NET runtime installed?

如果您的最终用户是有人用的技术经验，那么我们有理由牺牲一些MSI软件包的wizardness的东西多了几分原始的，如Ruby脚本，PowerShell脚本或.NET的灵活性控制台或Winforms应用程序。

If your end user is someone with technical experience then it seems reasonable to sacrifice some of the "wizardness" of an MSI package for the flexibility of something a little more raw, such as a Ruby script, Powershell script, or .NET console or Winforms app.

这篇关于C＃.NET - 部署＆QUOT;非常＆QUOT;自定义应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！