Native c++ using VC++ 8.0
-
Can I write native C++ code which will run without the help of .NET Framework in VC++ 8.0? I tried New Project -> VC++ -> Win32 -> Win32 Project. But it is not working without the help of Framework. Regards, Hogan
hogan.john wrote:
But it is not working without the help of Framework.
How did you confirm that?
nave [OpenedFileFinder]
-
hogan.john wrote:
But it is not working without the help of Framework.
How did you confirm that?
nave [OpenedFileFinder]
VC++ 8.0 and Framework 3.5 installed in my development machine. So I build it then copied the release folder into another machine that doesn’t have Framework. It showed the error message “The application is failed to start because the configuration is incorrect”. I assume this error because of the lack of framework. Please let me know is it possible to write native code in VC++ 8.0 which will run without the help of Framework.
-
VC++ 8.0 and Framework 3.5 installed in my development machine. So I build it then copied the release folder into another machine that doesn’t have Framework. It showed the error message “The application is failed to start because the configuration is incorrect”. I assume this error because of the lack of framework. Please let me know is it possible to write native code in VC++ 8.0 which will run without the help of Framework.
it is not because of the .net Framework. But the vc++ runtime dlls may not be present in the target machine. you can download the run time from following site and install it on the other machine. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) [^]
nave [OpenedFileFinder]
-
it is not because of the .net Framework. But the vc++ runtime dlls may not be present in the target machine. you can download the run time from following site and install it on the other machine. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) [^]
nave [OpenedFileFinder]
Thanks for your great help. So we need at least this service pack on the target machine. This is annoying me. Every one said that VC++ 8.0 is the best modern compiler. But the programs developed in this required a helper software. Ok once again thanks for your kind response :-D
-
Thanks for your great help. So we need at least this service pack on the target machine. This is annoying me. Every one said that VC++ 8.0 is the best modern compiler. But the programs developed in this required a helper software. Ok once again thanks for your kind response :-D
You can also link statically to the C-runtime library. I guess in that case you won't need to install the redist package. Not sure because I never worked with VC2008. Of course in that case your exe will be larger.
Cédric Moonen Software developer
Charting control [v1.4] -
Thanks for your great help. So we need at least this service pack on the target machine. This is annoying me. Every one said that VC++ 8.0 is the best modern compiler. But the programs developed in this required a helper software. Ok once again thanks for your kind response :-D
No you don't necessarily have to install this, you can also copy DLL's along with the executable. The DLL's needed to be redistributed are in the folder "Microsoft Visual Studio 8.0\VC\redist\x86". I think VC++ Express Edition do not come with "redist" folder, however, there is a solution discusses here[^]. There is an article here at codeproject discussing this same issuse (link[^]). Look at "Install a private assembly" section. Lastly you can link with CRT DLL's statically so that there are no dependencies. Also this is not specific to VC++, such dependencies will always be there no matter what compiler you will use. It might be easier to do this for other compilers but they will be there. There will always be libraries you link with and have to install them on user machine. -Saurabh
-
You can also link statically to the C-runtime library. I guess in that case you won't need to install the redist package. Not sure because I never worked with VC2008. Of course in that case your exe will be larger.
Cédric Moonen Software developer
Charting control [v1.4]I am sorry if my curiosity irate you. If there is no problem can tell me which tool you are using to develop C++ applications? :) Regards, Hogan
-
No you don't necessarily have to install this, you can also copy DLL's along with the executable. The DLL's needed to be redistributed are in the folder "Microsoft Visual Studio 8.0\VC\redist\x86". I think VC++ Express Edition do not come with "redist" folder, however, there is a solution discusses here[^]. There is an article here at codeproject discussing this same issuse (link[^]). Look at "Install a private assembly" section. Lastly you can link with CRT DLL's statically so that there are no dependencies. Also this is not specific to VC++, such dependencies will always be there no matter what compiler you will use. It might be easier to do this for other compilers but they will be there. There will always be libraries you link with and have to install them on user machine. -Saurabh
Thanks for that link. It really help me
-
Thanks for that link. It really help me
You are welcome. -Saurabh
-
I am sorry if my curiosity irate you. If there is no problem can tell me which tool you are using to develop C++ applications? :) Regards, Hogan
I'm using VC2005 :)
Cédric Moonen Software developer
Charting control [v1.4] -
You are welcome. -Saurabh
I had the saem problem as you. I could not get my programs tio run on a machine with just the OS. Now I 1) Change the Project defaults in the General Section to "Use MFC in a static library" 2) Uncheck "Inherit from Parent or project defaults" in the linker Additional Library Directories section (gets rid of a warning). All my programs work on a machone with a "virgin" OS after these changes.
-
I had the saem problem as you. I could not get my programs tio run on a machine with just the OS. Now I 1) Change the Project defaults in the General Section to "Use MFC in a static library" 2) Uncheck "Inherit from Parent or project defaults" in the linker Additional Library Directories section (gets rid of a warning). All my programs work on a machone with a "virgin" OS after these changes.
Statically linking is okay for projects which do not depend on other 3rd party components using MFC. If you link MFC statically in your project and use a component with dynamically linked MFC then there will be problems. -Saurabh