installshield和Visual Studio 2012 [英] installshield and Visual Studio 2012

问题描述

我们都知道Installshield对我们的VS来说是一件糟糕的事情吗？



微软会坚持下去我认为未来25年，无论如何。



我一直在尝试使用Installshield创建一个安装项目一周，当我在虚拟机中设置它时它不起作用！



我试图为我的桌面应用程序创建一个安装项目，其中包含.NET 4和SQL Server 2012 Express的先决条件以及我成功创建的所有内容。



问题在于数据库，如何将它包含在我的项目中以及它的正确连接字符串是什么？



我将它与我的SQL Server分离并将其与输出文件放在一起并且它从未起作用。

We all know that Installshield is an awful thing lay with our VS right ?

Microsoft will stick to it I think for the next 25 decades, any way.

I have been trying to create a setup project with Installshield for a week now and when I set it up in my virtual machine it does not work!

I seek to create a setup project for my desktop app with prerequisites for .NET 4 and SQL Server 2012 Express and all of that I succeeded to create.

The problem is in the database, how can I include it to my project and what is the proper connection string for it?

I detached it from my SQL Server and put it with the output file and it never worked.

推荐答案

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



我的解决方案是使用开源安装工具集开源WiX：

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

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?

My solution is using open-source WiX, the open-source installation toolset:
http://en.wikipedia.org/wiki/WiX[^],
http://wixtoolset.org/[^].

I recently 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

Sergey为InstallShield提供了一个可能的替代品....好吧，另一个是InnoSetup。它是一个开源解决方案，它通过支持Pascal为您提供编程选项。它确实很好用，非常灵活。我已经使用了InstallShield多年，后面真的很痛苦，我只是开始使用InnoSetup而且我已经更喜欢它了。



这是链接到他们的网站：

http://www.jrsoftware.org/isinfo.php [< a href =http://www.jrsoftware.org/isinfo.phptarget =_ blanktitle =New Window> ^ ]



他们支持：

- 预编译指令的预处理器

- Pascal脚本在安装过程中几乎任何时候都具有灵活性

- 相对容易学习（GUI使其易于使用）

Sergey offered one possible replacement for InstallShield....well, another is InnoSetup. It's an open source solution and it offers you a programming option by supporting Pascal. It really does work pretty well and is very flexible. I've used InstallShield for years and it's really a pain in the rear, I've only started using InnoSetup and I already like it better.

Here's the link to their site:
http://www.jrsoftware.org/isinfo.php[^]

They support:
- A pre-processor for pre-compilation directives
- Pascal scripting for flexibility at pretty much any point in the installation process
- Relatively easy to learn (GUI makes it easy to start to use)

这篇关于installshield和Visual Studio 2012的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！