在Visual Studio 2013中使用InstallShield Limited Edition创建安装文件 [英] Making setup file using InstallShield Limited Edition in Visual Studio 2013

问题描述

晚上好，



我使用C＃2013完成了我的项目，现在我正在尝试使用 InstallShield Limited Edition 创建安装文件但最后出现了一些消息错误，调试器无法继续运行无法开始调试的过程..



有人可以帮助我这样做吗，请求？

Good evening,

I finished my project using C# 2013 and now I'm trying to make setup file using InstallShield Limited Edition but some message error comes in the last which is "debugger cannot continue running the process unable to start debugging"..

could someone help me to do that, pleas?

推荐答案

你愿意尝试替代方案，这很好。我会试着解释为什么它会有很多意义。请查看我过去的答案：

自定义安装项目 [ ^ ]，

installshield和Visual Studio 2012 [ ^ ]，

如何基于处理器架构类型（32位或64位）有条件地安装组件？ [ ^ ]，

如何根据处理器架构类型（32位或64位）有条件地安装组件？ [ ^ ]。



Installshield非常糟糕。与Visual Studio捆绑的许多版本的安装项目类型也不好;微软正在摆脱它而不用其他任何东西替换它。那么，该怎么办？



Plrase见：

http://en.wikipedia.org/wiki/WiX ，

http：// wixtoolset。 org 。



不久前，我已经迁移到它，我很高兴我做到了。它也不完美（整个Microsoft Installer及其API远远落后于其他技术），但它比我迄今为止听过的任何内容都要好得多。实际上，如果你使用WiX，你会明白上面提到的工具实际上几乎是非法的（技术上），他们正在使用他们的专有项目文件。只有WiX能够很好地符合现代MSBuild和相关的基于XML的项目标准，因此您可以使用标准MSBuild技术来使用WiX项目：定制它，与更大的主项目或解决方案集成，编写您自己的扩展，如果您需要的话，以及等等。



此外，它与不同版本的Visual Studio非常顺畅地集成。



最后，一个很大的好处是：WiX代码是非可视的。使用一些官方记录的XML方案，在XML代码中显式声明了所有内容。 XML代码文件背后没有任何内容。



关于行为和功能，很遗憾，很多高级功能都没有全面记录。但社区已经收集了大量经验并提供了许多有用的建议。到目前为止，我能够找到我真正需要的所有家务的解决方案。并且我在旧版安装项目中找到了一套随时可用的解决方案。需要开发自定义步骤的一些操作已经嵌入到WiX中。它包括调整Windows防火墙到您的应用程序，设置文件和目录的权限，根据项目平台和目标平台的不同操作，以及更多。



WiX源代码是可用的，但是，在我使用的版本中，它没有编译。记录了这个问题。我希望这个产品的问题会随着时间的推移而修复。

-SA

It's good that you are willing to try the alternative. I'll try to explain why it will make a lot of sense. Please see my past answers:
Custom setup project[^],
installshield and Visual Studio 2012[^],
How to conditionally install components based on processor architecture type (32-bit or 64-bit)?[^],
How to conditionally install components based on processor architecture type (32-bit or 64-bit)?[^].

Installshield is awful. And the setup project type bundled with many versions Visual Studio is not good, too; Microsoft is getting rid of it without replacing it with anything else. So, what to do?

Plrase see:
http://en.wikipedia.org/wiki/WiX,
http://wixtoolset.org.

A while ago, I've made a migration to it and am very glad I did. It's not perfect too (and the whole Microsoft Installer and its API is well behind other technologies), but it is much better than anything I ever heard of so far. Actually, if you use WiX, you will understand that the tools mentioned above are actually nearly illegal (technically), they are using their proprietary project files. Only WiX provide excellent compliance with the contemporary MSBuild and related XML-based project standard, so you can use WiX projects using standard MSBuild techniques: customize it, integrate with bigger master projects or solutions, write your own extensions, if you need some, and so on.

Also, it has very good and smooth integration with Visual Studio of different versions.

Finally, one big benefit is: WiX code is non-visual. Everything is explicitly declared in XML code using some official documented XML scheme. Nothing is hidden behind the XML code files.

As to the behavior and features, many advanced features are not comprehensively documented, unfortunately. But communities already collected considerable experience and provide a lot of useful advice. So far, I was able to find solutions to all chores I practically needed. And the set of ready-to-use solutions is wider that that I found in a legacy Setup project. Some actions which required development of custom steps are already embedded in WiX. It includes adjusting Windows Firewall to your application, setting permissions of files and directories, different action depending on the project platform and target platform, and a lot more.

The WiX source code is available, but, in the version I used, it did not compile. This problem was documented. I hope the problem of this product will be fixed with time.

—SA

试试此 [ ^ ]

这篇关于在Visual Studio 2013中使用InstallShield Limited Edition创建安装文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！