Visual Studio 2010 中的 InstallShield 2011 LE 出现内部生成错误 - WPF 桌面应用程序安装程序

发布于 2025-01-04 03:39:12 字数 361 浏览 2 评论 0原文

我已在 Visual Studio 2010 中启用了 InstallShield 2011 LE,并尝试使用它构建我的第一个安装程序。我的应用程序是 WPF / .NET 4.0 应用程序。该解决方案相当繁重,约有 30 个项目,其中大多数是 Prism 模块。

每当我构建解决方案时,InstallShield 在构建文件表步骤期间或之后都会给出“-6213 内部构建错误”,并且其日志中没有更多信息。它可能不相关,但我发现 Visual Studio 在使用此 InstallShield 安装项目时极其不稳定。它已经崩溃过很多次了。

我已经能够通过一个非常简单的 WPF 测试解决方案以这种方式成功创建安装程序。

谁能给我任何有关如何进一步调试的指示?

I've enabled InstallShield 2011 LE within Visual Studio 2010 and am trying to get my first installer built with it. My application is a WPF / .NET 4.0 application. The solution is quite heavy with about 30 projects, most of them Prism modules.

Whenever I build my solution InstallShield gives me a "-6213 Internal build error" during or after the Building File Table step with no further information in its log. It may not be related but I have found Visual Studio to be extremely unstable while working with this InstallShield setup project. It has crashed numerous times.

I have been able to create an installer successfully this way from a very simple WPF test solution.

Can anyone give me any pointers on how to debug this further?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

安人多梦 2025-01-11 03:39:12

InstallShield 有一个我讨厌的功能,称为依赖扫描。它基本上是扫描您的程序集并自动找出您想要部署的内容的地方。听起来不错,对吧?好吧,在我的世界里,这是把责任押在确定性地编写安装程序中的内容和不包含的内容上。许多刚接触安装程序的人都想拒绝相信我,这是你这样做的权利。但如果是我,我就会把它关掉。

所以基本上链接的文档说有一个未知原因的错误会在扫描期间破坏构建。我的猜测是,您在 Prism 中所做的事情超出了 InstallShield 可以处理的范围,因此您的构建失败了。

我要提到的是,StackOverlow 贡献者 Michael Urman 恰好在 InstallShield 工作,如果您有一个可重现的场景,他可能有兴趣从您那里获取一些测试数据。

Q109089:ERRDOC:构建错误 6213

InstallShield has a feature that I detest called Dependency Scanning. It's basically where it scans your assemblies and automagically figures out what you meant to deploy. Sounds great, right? Well, in my world that's punting responsibility for determinstically authoring what does and doesn't go into the installer. Many people new to installers want to refuse to believe me and that's your right to do so. But if it was me, I'd turn this off.

So basically the linked document says there is a bug of unknown cause that will break the build during this scanning. My guess is that something you are doing in Prism is way out of bounds of what InstallShield can handle so poof goes your build.

I will mention though that fellow StackOverlow contributor Michael Urman happens to work for InstallShield and if you have a reproducible scenario he just might be interested in getting some test data from you.

Q109089: ERRDOC: Build Error 6213

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文