after change an unmanagered exe to support clr.old syntax

[Guest]

I have a project, which is an unmanaged .exe file. It runs good after install
it in a machine, which has no vs.net installed. But it has .net framwork 2.0.
But after we set the support clr/old syntax for this project. It compiles and
runs good in a developer machine, but when we install it in the machine,
which has no vs.net with .net framework 2.0, then it has error: AppName
xxx.exe AppVer: 0.41.414.0 Modname: mscorwks.dll ModVer: 2.0.50727.42 offset:
00095f28.

Is anyone have idea what going on?
Thanks.

 

[Sheng Jiang[MVP]]

If you add CLR support to your project you need to deploy .Net framework
with your project output.

 

[Ben Voigt [C++ MVP]]

I have a project, which is an unmanaged .exe file. It runs good after
install
it in a machine, which has no vs.net installed. But it has .net framwork
2.0.
But after we set the support clr/old syntax for this project. It compiles
and
runs good in a developer machine, but when we install it in the machine,
which has no vs.net with .net framework 2.0, then it has error: AppName
xxx.exe AppVer: 0.41.414.0 Modname: mscorwks.dll ModVer: 2.0.50727.42
offset:
00095f28.

Is anyone have idea what going on?

If you are using Visual Studio SP1, you'll need the updated C++ libraries
(vcredist_x86.exe)