Original Post
🔒 Locked
Basic MFC question
Advertisement
What you need to do is include the necessary .dlls the application needs. To find out which ones, you need to use something like "Dependecy Walker", which comes with Visual Studio 6. I am not sure if it comes with 7, but all you do is run the program, tell it to open your .exe and it tells all the .dlls that the .exe 'depends' on to run. Once you include those .dlls, then someone else can run your program.
Alternativley, you can go to Project Options, and choose to link MFC statically instead of using a shared .dll. That owuld be your best bet. It is what I did for testing my Audio Library so I didn't have to distribute out the .dlls.
- Drew
Alternativley, you can go to Project Options, and choose to link MFC statically instead of using a shared .dll. That owuld be your best bet. It is what I did for testing my Audio Library so I didn't have to distribute out the .dlls.
- Drew
With MSVC 6, the dll you need is "mfc42.dll" I believe. I could be wrong of course. If you run the application on a machine without the correct DLLs, it'll say what DLL is missing ("The application cannot find blah.dll in the path [Huge great long path string]")
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement