MFC42.DLL
-
i tried that but not got solution, still facing the same problem....
-
when i execute my MFC exe file on a machine not installed with Visual studio, i get an error saying, "coudnot find MFC42D.DLL, try reinstalling application and run again". i m not able to resolve this, can anybody please help??? rishi
MFC42D.DLL is the debug version of the MFC library and is only installed with Visual Studio. If you compile your program as a release version, it will use MFC42.DLL which is present on all Windows systems. Steven
-
As explained before, you should use Dependency Walker to check which dll are required by your application. You should also distribute the release version of your application, not the debug one (legally, you are not allowed to do so).
Cédric Moonen Software developer
Charting control [v1.2]Where is this Dependency Walker to be found? I will most probably need it as well. Another question... Can dynamic and static linking be mixed? I mean... Can I tell my programm to statically link the MFC dlls that are needed but in other part of the programm to be able to choose a specifical dll to do some tasks but allowing to change it with other two (depending on what i want to do)???
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
-
i tried that but not got solution, still facing the same problem....
-
Where is this Dependency Walker to be found? I will most probably need it as well. Another question... Can dynamic and static linking be mixed? I mean... Can I tell my programm to statically link the MFC dlls that are needed but in other part of the programm to be able to choose a specifical dll to do some tasks but allowing to change it with other two (depending on what i want to do)???
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Nelek wrote:
Where is this Dependency Walker to be found? I will most probably need it as well.
Nelek wrote:
Can I tell my programm to statically link the MFC dlls that are needed but in other part of the programm to be able to choose a specifical dll to do some tasks but allowing to change it with other two (depending on what i want to do)???
Sorry, but I don't really understand what you mean. What are those 'specifical' dll's you talk about ? Some third party dll's that you are using for your application ? Changing the settings about MFC statically or dynamically linked will only affect how the MFC libraries will be linked to your application. This has absolutely no impact on what you do with other dll's.
Cédric Moonen Software developer
Charting control [v1.2] -
Nelek wrote:
Where is this Dependency Walker to be found? I will most probably need it as well.
Nelek wrote:
Can I tell my programm to statically link the MFC dlls that are needed but in other part of the programm to be able to choose a specifical dll to do some tasks but allowing to change it with other two (depending on what i want to do)???
Sorry, but I don't really understand what you mean. What are those 'specifical' dll's you talk about ? Some third party dll's that you are using for your application ? Changing the settings about MFC statically or dynamically linked will only affect how the MFC libraries will be linked to your application. This has absolutely no impact on what you do with other dll's.
Cédric Moonen Software developer
Charting control [v1.2]One of those dlls is a third party, the rest have to be programmed by me and used in my programm. One dll will be the main, calling the third party dll and choosing which of my dlls have to be used according to the objective tasks. The problem is that I'm completely newbie with DLLs, I know that I have to read info (I'm already searching documentation) but I need to think about the structure to give a little schema to my boss as he wants :doh:. So resuming. My programm may be used in computers where no visual studio is installed, so I have to pack the needed MFC DLLs in the same place as my exe. Or statically link them, that would make to have them integrated in my exe (difference will be in exe's size). And with the others... I have thought to statically link the main dll because it will always used, and the others dinamically to be choosen when needed. It's this more or less correct (if possible)? Thanks and sorry for such a newbie question
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
-
One of those dlls is a third party, the rest have to be programmed by me and used in my programm. One dll will be the main, calling the third party dll and choosing which of my dlls have to be used according to the objective tasks. The problem is that I'm completely newbie with DLLs, I know that I have to read info (I'm already searching documentation) but I need to think about the structure to give a little schema to my boss as he wants :doh:. So resuming. My programm may be used in computers where no visual studio is installed, so I have to pack the needed MFC DLLs in the same place as my exe. Or statically link them, that would make to have them integrated in my exe (difference will be in exe's size). And with the others... I have thought to statically link the main dll because it will always used, and the others dinamically to be choosen when needed. It's this more or less correct (if possible)? Thanks and sorry for such a newbie question
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Nelek wrote:
And with the others... I have thought to statically link the main dll because it will always used, and the others dinamically to be choosen when needed.
Nope, you can't statically link with dll's. In case of MFC, they gave you the choice because they provide both versions: dll or static library, so you can simply choose which one you use. In the case of third party dll's, you won't have the choice, you need to distribute them with your application (except if they provide a static library too, which I doubt).
Cédric Moonen Software developer
Charting control [v1.2] -
Nelek wrote:
And with the others... I have thought to statically link the main dll because it will always used, and the others dinamically to be choosen when needed.
Nope, you can't statically link with dll's. In case of MFC, they gave you the choice because they provide both versions: dll or static library, so you can simply choose which one you use. In the case of third party dll's, you won't have the choice, you need to distribute them with your application (except if they provide a static library too, which I doubt).
Cédric Moonen Software developer
Charting control [v1.2]From the others DLLs there is only one third party DLL, the rest have to be programmed by me. And there is where I don't know how to start with :sigh::confused: Actually I would prefer to programm my functions in a new module/class and just calling the third party dll to stablish the connection when needed, but my boss wants to do it in different dlls and that is what confuse me. Once the connection is made, I should theoretically be able to read from / write to with usual functions. I know that I need to learn about DLLs and more in programming but the fucking project has a deadline and I'm afraid about it :~
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
-
when i execute my MFC exe file on a machine not installed with Visual studio, i get an error saying, "coudnot find MFC42D.DLL, try reinstalling application and run again". i m not able to resolve this, can anybody please help??? rishi
See here, particularly the last part.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
-
when i execute my MFC exe file on a machine not installed with Visual studio, i get an error saying, "coudnot find MFC42D.DLL, try reinstalling application and run again". i m not able to resolve this, can anybody please help??? rishi
And if your loads a DLL at run time, you wont be able to check this with "depends". So you need to check what are the dlls your exe might use and check "depends" for all these dlls. Otherwise it would keep on failing !
Jemmy : Deadline? Pfft, a real programmer eats deadlines for breakfast. :P Mark: I thought real programmers ignored deadlines :sigh: Best wishes to Rexx[^]
-
can you please elaborate what do you mean by release configuration??? and also if you can guide me in how to incorporate MS Office package file into my API thanks
-
As explained before, you should use Dependency Walker to check which dll are required by your application. You should also distribute the release version of your application, not the debug one (legally, you are not allowed to do so).
Cédric Moonen Software developer
Charting control [v1.2]if you don't mind can you please explain how to check and use Dependency Walker???? thanks
-
can you please elaborate what do you mean by release configuration??? and also if you can guide me in how to incorporate MS Office package file into my API thanks
rishimohan wrote:
can you please elaborate what do you mean by release configuration???
There will be two build configuration by default. Debug and Release. You can change it through Build -> Set Active Project Configuration...
rishimohan wrote:
and also if you can guide me in how to incorporate MS Office package file into my API
Sorry, not so sure...
- NS -
-
MFC42D.DLL is the debug version of the MFC library and is only installed with Visual Studio. If you compile your program as a release version, it will use MFC42.DLL which is present on all Windows systems. Steven
THANKS A TON....it worked.... 1 more help required please, how to incorporate MS Office package file in my API????
-
rishimohan wrote:
can you please elaborate what do you mean by release configuration???
There will be two build configuration by default. Debug and Release. You can change it through Build -> Set Active Project Configuration...
rishimohan wrote:
and also if you can guide me in how to incorporate MS Office package file into my API
Sorry, not so sure...
- NS -
THANKS A TON.... it worked....
-
See here, particularly the last part.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
THANKS FOR THE LINK... it should help, i'll study this and come back but my specific requirement is that, i want my API to be executed when somebody tries to open a specific pre decided file of MS Office package.... can u help me with this or some kind of referrence ????
-
THANKS A TON.... it worked....