I have a question regarding the development of native C++ executables within Visual Studio 2005.
In past versions of of VS, like version 6, you could build your executable and most all OS' would have the msvcrt.dll and whatever other files needed to run the executable in a stand alone manor.
It has come to my attention that building a "stand alone" exe with VS2005 may not be possible at this point. Even though I am developing in a purely "native" capacity, the executable still does some funky .net stuff in the background (with manifests, something called side-by-side assemblies and something to do with isolation). After installing the .net 2.0 framework on the target machine the exe ran perfectly.
I tried disabling some options with the project; like telling it not to embed a manifest and saying no to isolation. This only makes the exe dead in the water, saying stuff like it loaded c runtimes incorrectly or something to that effect.
Does anyone know if .NET 2.0 is required on the target machine for native C++ exes to run properly, or is there some way to get around this?
Best regards,
Nathan Martini
In past versions of of VS, like version 6, you could build your executable and most all OS' would have the msvcrt.dll and whatever other files needed to run the executable in a stand alone manor.
It has come to my attention that building a "stand alone" exe with VS2005 may not be possible at this point. Even though I am developing in a purely "native" capacity, the executable still does some funky .net stuff in the background (with manifests, something called side-by-side assemblies and something to do with isolation). After installing the .net 2.0 framework on the target machine the exe ran perfectly.
I tried disabling some options with the project; like telling it not to embed a manifest and saying no to isolation. This only makes the exe dead in the water, saying stuff like it loaded c runtimes incorrectly or something to that effect.
Does anyone know if .NET 2.0 is required on the target machine for native C++ exes to run properly, or is there some way to get around this?
Best regards,
Nathan Martini