VS C++ project: does not work another computer
-
hello all, I have a simple project created by using Visual studio 2005(using MFC, complied in debug mode), it works at my computer, But it does not work another computer where not installed visual studio 2005, I know this is dlls issue, But i want to know what dlls i should copy with the application(.exe file), or another way to do it? Thanks in advance
It is never late to learn
-
hello all, I have a simple project created by using Visual studio 2005(using MFC, complied in debug mode), it works at my computer, But it does not work another computer where not installed visual studio 2005, I know this is dlls issue, But i want to know what dlls i should copy with the application(.exe file), or another way to do it? Thanks in advance
It is never late to learn
You have to make a release version of your program and install vcredist_x86.exe on the target machine. It can be dowloaded here[^]. If you have the VC SP1, scroll down the page to get the version for the SP1.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
hello all, I have a simple project created by using Visual studio 2005(using MFC, complied in debug mode), it works at my computer, But it does not work another computer where not installed visual studio 2005, I know this is dlls issue, But i want to know what dlls i should copy with the application(.exe file), or another way to do it? Thanks in advance
It is never late to learn
-
MFC42D.DLL MFCN42D.DLL MFCO42D.DLL MSVCRTD.DLL paste these dll on system32. It will solve your problem. :)
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
:~ He's talking about VC2005, not VC6.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
MFC42D.DLL MFCN42D.DLL MFCO42D.DLL MSVCRTD.DLL paste these dll on system32. It will solve your problem. :)
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
I use Visual Studio 2005, those dlls should be like these: MFC80D.DLL MFCN80D.DLL MFCO80D.DLL MSVCRTD.DLL But, still not clear, Why should use always copy the dlls into system, my program is like 0.4 mb, the dlls are about 10 mb For the simple project, why should i hold the dlls
It is never late to learn
-
MFC42D.DLL MFCN42D.DLL MFCO42D.DLL MSVCRTD.DLL paste these dll on system32. It will solve your problem. :)
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
Shilpi Boosar wrote:
MFC42D.DLL
mfc42d.dll is used by vc6. The mfc dlls with VS 2005 starts with mfc80
nave [OpenedFileFinder]
-
:~ He's talking about VC2005, not VC6.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
MFC42D.DLL MFCN42D.DLL MFCO42D.DLL MSVCRTD.DLL paste these dll on system32. It will solve your problem. :)
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
i.e the ugly way. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke -
You have to make a release version of your program and install vcredist_x86.exe on the target machine. It can be dowloaded here[^]. If you have the VC SP1, scroll down the page to get the version for the SP1.
Cédric Moonen Software developer
Charting control [v1.4 - Updated]Hello, Thanks for your reply I made a release mode, but it does work as debug mode, that is one thing. Another thing, do u think that Installing vcredist_x86.exe on the target machine, to run my application? Thanks
It is never late to learn
-
Hello, Thanks for your reply I made a release mode, but it does work as debug mode, that is one thing. Another thing, do u think that Installing vcredist_x86.exe on the target machine, to run my application? Thanks
It is never late to learn
Gofur Halmurat wrote:
Another thing, do u think that Installing vcredist_x86.exe on the target machine, to run my application?
:confused: sorry, I didn't understand the question. If you want to run your application on the target machine, then you'll need to execute vcredist_x86 on it. This will install the C-runtime libraries and the MFC libraries.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
Shilpi Boosar wrote:
u r Right
May I please ask you to STOP using SMS language on the boards? Don't you have a keyboard with all the keys in it? :|
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
Shilpi Boosar wrote:
u r Right
May I please ask you to STOP using SMS language on the boards? Don't you have a keyboard with all the keys in it? :|
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
u r right but plz help coz urgent... :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke -
Shilpi Boosar wrote:
u r Right
May I please ask you to STOP using SMS language on the boards? Don't you have a keyboard with all the keys in it? :|
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
Thanks For your suggestion Rajesh, but we are here to solve a issue not to solve writing scripts. and By the way please check your previous messages also prasad_som wrote: Do some study, and then come up with problems. I'll hold my breath and wait for her to come up with 'problems' for us to solve. BTW how are you doing? It's been a long time. [^]
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
-
u r right but plz help coz urgent... :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke -
MFC42D.DLL MFCN42D.DLL MFCO42D.DLL MSVCRTD.DLL paste these dll on system32. It will solve your problem. :)
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
The problem with this is that it is illegal to distribute the dlls you listed. Those are DEBUG builds, and per the Microsoft License Agreement, you may not re-distribute them. You must build a release build of your program, and then you are permitted to redistribute the release build of the dlls (using the vcredist as mentioned by others).
Karl - WK5M PP-ASEL-IA (N43CS) PGP Key: 0xDB02E193 PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
-
Thanks For your suggestion Rajesh, but we are here to solve a issue not to solve writing scripts. and By the way please check your previous messages also prasad_som wrote: Do some study, and then come up with problems. I'll hold my breath and wait for her to come up with 'problems' for us to solve. BTW how are you doing? It's been a long time. [^]
Yes U Can ...If U Can ,Dream it , U can do it ...ICAN
Using SMS lingo on a good public board like this is considered to be unprofessional, and I suggested you not to do it. I'm done.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
The problem with this is that it is illegal to distribute the dlls you listed. Those are DEBUG builds, and per the Microsoft License Agreement, you may not re-distribute them. You must build a release build of your program, and then you are permitted to redistribute the release build of the dlls (using the vcredist as mentioned by others).
Karl - WK5M PP-ASEL-IA (N43CS) PGP Key: 0xDB02E193 PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
-
I use Visual Studio 2005, those dlls should be like these: MFC80D.DLL MFCN80D.DLL MFCO80D.DLL MSVCRTD.DLL But, still not clear, Why should use always copy the dlls into system, my program is like 0.4 mb, the dlls are about 10 mb For the simple project, why should i hold the dlls
It is never late to learn
You could build the project using MFC in a static library instead of moving debug dlls. But this might also generate huge executable.
