运行 Visual Studio 2005 中生成的 .EXE 文件失败
我想运行一个用 Visual Studio 2003 制作的 .exe 文件，但每次在 Windows 7 计算机、Vista 计算机和 XP 计算机上运行它时都会出现错误。 Windows 7 和 Vista 上的错误显示“应用程序已停止工作”，然后让我关闭错误框。
在 Windows XP 中，错误略有不同，“应用程序无法运行 (0xc0000135) 单击“确定”终止应用程序。”
I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
该错误代码似乎表明应用程序未能正确初始化。
预期的 .NET 版本可能不存在。
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
据我所知，VS 2003 默认情况下针对 .NET 1.1 库进行编译。没有直接的方法可以在 Windows 7 或 Vista 机器上安装它。您是否需要针对 .NET 1.1 库进行编译，或者您可以在 VS2005 中加载它，将输出 .net 版本更改为 2.0 或更高版本，然后重新编译应用程序吗？
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
如果您有应用程序的源代码，请尝试在调试模式下运行应用程序并逐行逐步执行，直到找到异常。如果您没有源代码，可以尝试在几种不同的兼容模式下运行该应用程序。另一个可以尝试的选择是检查 Windows 事件日志以获取更具体的信息。
如果您想真正深入了解它，可以使用 SysInternals ProcMon.exe 并筛选失败的 exe，以查看失败期间发生的 WinAPI 调用。
此外，对论坛的基本搜索表明错误通常伴随着框架问题。重新编译应用程序或在 VS2003 项目设置中检查所需的框架。
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.