I have succeeded in creating the setup.exe and it runs to completion. But on clicking the icon created I get an error message box stating: "Application has stopped working" with the 3 options, Close, Debug, check for online solutions.
我已成功创建setup.exe并运行完成。但是在点击创建的图标时，我收到一个错误消息框，说明：“应用程序已停止工作”，有3个选项，关闭，调试，检查在线解决方案。
The details of the problem are:
问题的细节是：
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: zed axis.exe
Problem Signature 02: 10.0.4925.7882
Problem Signature 03: 51cadd13
Problem Signature 04: Zed Axis
Problem Signature 05: 10.0.4925.7882
Problem Signature 06: 51cadd13
Problem Signature 07: 4d69
Problem Signature 08: b
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.2.9200.2.0.0.256.72
Locale ID: 1033
My guess was that it cant find the .exe file. But I don't know where I am going wrong could you help me resolve this.
我的猜测是它无法找到.exe文件。但我不知道我哪里出错了你能帮我解决这个问题。
1 个解决方案
#1
0
FWIW, some people think that it's InstallShield (or similar tools) job to autodetect your dependencies and author them for you. In fact, InstallShield does have some functionality to achieve this. But IMO it's a hopeless attempt. For any programming endeavor step 1 is to determine the requirements and step 2 is to implement them.
FWIW，有些人认为它是InstallShield（或类似工具）的工作，可以自动检测您的依赖项并为您创作。事实上，InstallShield确实有一些功能来实现这一目标。但IMO这是一次毫无希望的尝试。对于任何编程努力，步骤1是确定要求，步骤2是实现它们。
Many will argue that the point of spending $ on InstallShield is to automate this. I couldn't disagree more. Automation is nice but at the end of the day it's my job to understand my deployment requirements and validate that they are implemented correctly.
许多人会争辩说，在InstallShield上花费$是为了实现自动化。我不能不同意。自动化很不错，但最终我的工作是了解我的部署要求并验证它们是否正确实施。
You need to profile your application to understand what file is missing, add it to your installer and rinse and repeat. This could simply mean looking at the code, or using ILDASM or .NET Reflector or even ProcessExplorer to determine the missing component.
您需要对应用程序进行概要分析，以了解缺少的文件，将其添加到安装程序中并进行冲洗和重复。这可能只是意味着查看代码，或使用ILDASM或.NET Reflector甚至ProcessExplorer来确定缺少的组件。
#1
0
FWIW, some people think that it's InstallShield (or similar tools) job to autodetect your dependencies and author them for you. In fact, InstallShield does have some functionality to achieve this. But IMO it's a hopeless attempt. For any programming endeavor step 1 is to determine the requirements and step 2 is to implement them.
FWIW，有些人认为它是InstallShield（或类似工具）的工作，可以自动检测您的依赖项并为您创作。事实上，InstallShield确实有一些功能来实现这一目标。但IMO这是一次毫无希望的尝试。对于任何编程努力，步骤1是确定要求，步骤2是实现它们。
Many will argue that the point of spending $ on InstallShield is to automate this. I couldn't disagree more. Automation is nice but at the end of the day it's my job to understand my deployment requirements and validate that they are implemented correctly.
许多人会争辩说，在InstallShield上花费$是为了实现自动化。我不能不同意。自动化很不错，但最终我的工作是了解我的部署要求并验证它们是否正确实施。
You need to profile your application to understand what file is missing, add it to your installer and rinse and repeat. This could simply mean looking at the code, or using ILDASM or .NET Reflector or even ProcessExplorer to determine the missing component.
您需要对应用程序进行概要分析，以了解缺少的文件，将其添加到安装程序中并进行冲洗和重复。这可能只是意味着查看代码，或使用ILDASM或.NET Reflector甚至ProcessExplorer来确定缺少的组件。