Visual Studio 2008安装程序引导程序问题（setup.exe） [英] Problem with Visual Studio 2008 Installer Bootstrap (setup.exe)

问题描述

我有一个Visual Studio安装项目，它利用了我已迁移到VS 2008的先决条件安装程序引导程序（setup.exe）。我使用Winzip Self Extractor将setup.exe和.msi打包成一个可下载的.exe文件对于我的客户，他们只是运行我的.exe并解压缩并启动visual studio生成的setup.exe。

我刚注意到在升级到VS08之后，setup.exe的行为有点不同而且我的WinZip方法不再有效。过去发生的事情是setup.exe将一直运行，直到msiexec完成安装，WinZip只是等待setup.exe退出，然后才删除临时提取的文件。但是，现在，setup.exe立即退出并且不等待msi被安装，因此Winzip Self Extractor删除了msi文件（认为已经完成）。

我该怎么办？我正在考虑使用旧的setup.exe文件并将其与08生成的msi一起使用，或者只是完全放弃vdproj。是否有任何命令行标志我可以发送setup.exe使其行为与以前一样？

是否有任何关于我遇到的更改的文档？

I have a Visual Studio setup project that utilizes the Prerequisites installer bootstrap (setup.exe) which I have migrated to VS 2008.  I use Winzip Self Extractor to package the setup.exe and .msi into a single downloadable .exe file for my customers, they just run my .exe and it unpacks and kicks off the setup.exe generated by visual studio.

I just noticed that after the upgrade to VS08, that setup.exe behaves a bit differently and my WinZip approach no longer works.  What used to happen is the setup.exe would stay running until msiexec had completed the installation and WinZip would simply wait for the setup.exe to exit before deleting the temporary extracted files.  Now, though, setup.exe exits immediately and doesn't wait for the msi to be installed so Winzip Self Extractor deletes the msi file (thinking it's done).

What can I do about this?  I'm thinking of taking my old setup.exe file and using that with the 08-generated msi, or just ditching altogether the vdproj.  Are there any command line flags I can send setup.exe to have it behave in the same manner as before?

Is there any documentation regarding the change I've run into?

推荐答案

这篇关于Visual Studio 2008安装程序引导程序问题（setup.exe）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！