|
HI Marc,
By Mistake you post your answer to Wrong Guy!  ,
Right Guy, Who is looking for Answer is Tox.
Anyway 5x from Me
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
|
|
|
|
|
If you build your application in Release mode in VC++ 6.0
then i assure you don't need any dll files to attach to the CD.Your application will run on any other computer where Visual Studio is not installed without problems.
But if you do the same in VC++.Net 2003 then you'll need the
MFC71.dll file.
m0n0
|
|
|
|
|
quoting the MSDN (thanks to Alok) :
"Mfc42.dll needs to be redistributed with MFC applications unless you statically linked to the MFC DLL (that is, unless you specified Use MFC in a Static Library on the General tab in the Project Settings dialog box). Note that static linking to MFC is supported only in Visual C++ Professional and Enterprise Editions.
If you dynamically link your application to the MFC library, you will, at a minimum, need to redistribute Mfc42.dll and Msvcrt.dll. All MFC DLLs use the shared version of the C run-time library; thus, Msvcrt.dll is required.
"
so, revise your judgment...
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
Damn, you write faster than me 
|
|
|
|
|
cedric moonen wrote:
Damn, you write faster than me
yep... you didn't know ?
:->
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
cedric moonen wrote:
Damn, you write faster than me
I will Ask TOX to use only one finger for typing and that too be Left hand Left Most Finger 
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
|
|
|
|
|
Revising my judgment...
Mfc42.dll is automatically installed in the windows directory if you install win98/XP that is why you don't need to attach this file to your CD. Because if the user has win98/XP installed it means he already has this dll file.
I've done it many times and have never experienced problems.
As mfc71.dll was released after win98/xp , thats why you'll have to attach this file to CD if you are building your app in C++.Net 2003
m0n0
|
|
|
|
|
i still don't agree.
if MFC is already install, it has 2 reasons for me :
1. Visual studio is installed on the computer
2. Another application already copied the libraries to the computer
if you format and install windows wathever version, try executing an MFC program without its dlls... it won't work !
and i trust MSDN on this point !!
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
you can trust whom you want ...
I just told you my experience i ' ve copied my applications(simple exe-s,VC++ 6.0) to too many computers-s of my friends and not only who did not have Visual Studio installed and my app ran without any problems.
You can ask anybody that mfc42.dll is installed during the win98/xp install automatically.
Of course same did not work with app-s built on VC++.Net 2003
m0n0
|
|
|
|
|
toxcct wrote:
if MFC is already install, it has 2 reasons for me :
1. Visual studio is installed on the computer
2. Another application already copied the libraries to the computer
I agree. Point #2 is usually the reason that folks think MFC exists with native Windows.
toxcct wrote:
if you format and install windows wathever version, try executing an MFC program without its dlls... it won't work !
I agree again. This has happened to me on more than one occasion.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
|
|
|
|
|
DavidCrow wrote:
I agree. Point #2 is usually the reason that folks think MFC exists with native Windows.
i've searched for google to find out whether is mfc42.dll win native file and found this Here :
mfc42.dll (Microsoft Foundation Classes Library) - Details
The mfc42.dll library is required for windows to operate. It provides a number of classes and code functions that are used in a wide variety of programs written using the Visual C++ programming language. If mfc42.dll is unavailable, any software that relies on the functions that it provides will crash and/or become unstable.
i also got
THIS
answer on Microsoft forum , from an MVP
|
|
|
|
|
Look Here
"Go as far as you can see,and when you get there you’ll see further" - Unknown
|
|
|
|
|
Giorgi Moniava wrote:
Look Here
Ok Agreed Mr Moniava, Frankly Speaking i never ship MFC42.dll with any of my company product!
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
|
|
|
|
|
Giorgi Moniava wrote:
then i assure you don't need any dll files to attach to the CD
Nope ! Only if you choose to statically link the MFC to your project. Otherwise you still need an external dll containing the MFC's.
|
|
|
|
|
Nope ! Only if you choose to statically link the MFC to your project. That's what I have done in my most projects. Just wondering, if there is any reasons that should not be done, except an increase of overall application size.
Thanks
|
|
|
|
|
yes, increase of exe file size, and also for future evolutions...
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
Hi everyone, does anyone here know how to compress DICOM image to raw format and save image file into a binary file format as a 1 dimensional array. Mine is a 256x256 image. Can help me write a program to display the pixel value of black and white when i run the program.
|
|
|
|
|
Go and start your own thread...
Blog[^]
|
|
|
|
|
The main reason why this should not be done, is because MS will not be able to help you with updates if you statically link to their libs into your app.
Another good reason might be applicable when you develop a large application. The reason that comes to mind is: when you statically link to MFC's libraries, your link time will increase dramatically. This is not very pleasant if you have to wait a very long time before your application is linked together.
Blog[^]
|
|
|
|
|
Use depends.exe to see what dll's your exe needs. That's the sure way. But i'd reccomend against shipping kernel32.dll etc 
using System.Beer;
|
|
|
|
|
Run depends.exe and load your EXE. This is the best way to tell which DLL you need.
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
If i remember correctly you just make the executable file for your application in the release folder (ie release ) and not debug.It may solve the problem.If someone thinks that i am incorrect please give me a feedback.
Be FaithFull To Your Work.
|
|
|
|
|
nop, that's not it.
of course, when i compile the project, the exe file is located into the Debug or Release folder.
but if you read all the posts of the subject, i'd like to move the exe to a CD to be use on one's computer that is suspected not to have MFCxx.DLL on its system.
but it's ok now, i received many good answers to know what to do...
thanks
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
Could anybody tell me where can I find some free examples on developing an OPC C++ client and OPC servers?
Thanks
|
|
|
|
|
What I know they are some sort of COM objects. Starter can be possibly http://www.opcfoundation.org/[^]
but in fact I only heard that they exists, nothing more But I also heard that I'll about to develop some 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
