MFC Error when run

If it helps at all, this is the Code which is giving me this problem:

http://www.codeproject.com/internet/CustomBrowser.asp

If the other machine does not have Visual Sutio installed, you will have to make sure that a) you are trying to run a Release build (as opposed to a Debug build) and that b) all the necessary runtime DLLs are present, see http://msdn2.microsoft.com/en-us/library/ms235264.aspx ("Redistributing the MFC Library")

hi,

Visual studio 2005 you are using right.MAke sure that the other pc has .net framework installed or not

Deepu

Hi guys,

The machine I tested it on was Windows XP Professional (not at the machine at the moment, but pretty sure it's Service Pack 2). Wouldn't this already have the .NET Framework installed, or is there a later version required for 2005?

Cheers!

Hi guys,

I just double checked, and the machine has the .NET Framework 2.0 installed on it already. What else would you say I should install?


jkr,

I read your link, and it said I'm meant to have something installed, but what? I've got the .NET Framework 2.0 installed, and the code is Compiled in Release Build, but still gives me this error...

Hi jkr,

That looks like a VERY impressive application, I'll give it a go in an hour, I need to finish off some work first.

Cheers!

Hi jkr,

It's showing me a lot of DLL's, but not sure really how to make use of this application, could you possibly give me a quick run-through of what I am supposed to look at, to verify which files are required? Or is there possibly a way of create an Install of this EXE which will automatically include any DLL's required on other machines?


Cheers!

All you need to do is to check for DLLs that are reported as "missing". These are displayed with a red icon. I am pretty sure that Msvcr80.dll and Mfc80.dll will be among them.

OK, well the only ones I have coming up as missing are:

EFSADU.DLL
MSJAVA.DLL

but I also have this one in red with a sand-timer:

MPR.DLL

MPR.DLL is not important (the sand-timer stands for 'delay load') - but, are you testing that on the non-development machine?

Valid point, sorry jkr, I tested that on the machine which has Studio 2005 on it.

I'll test it on the other machine now, and reply shortly with the results.

I'm getting:

MFC80D.DLL
MSVCR80D.DLL
MSJAVA.DLL
MPR.DLL


and got:

Error: At least one required implicit or forwarded dependency was not found.
Error: The Side-by-Side configuration information in "c:\documents and settings\justin\desktop\CUSTOMBROWSER.EXE" contains errors. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001).
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

Hm, the trailing 'D' indicates a debug build - that you cannot run on machines that do not have VC++ installed. Switch to a Release build first.

Sorry, I ran the program on the Debug version by accident. I will try again on the Release build now, and paste the results shortly...

I just went to:

Build->Configuration Manager

and it says:

Project, Configuration, Platform, Build
CustomBrowser, Release, Win32, True


And I still get the 'D' which you said indicated a debug build. Am I doing something wrong?

Are you sure you switched to release for all the components involved?

Hi jkr,

I made a presumption that what I did was for the entire project rather than for each component, do I need to open each *.cpp/*.h file and do the same?

No, I thopught that the project might create more than one binary, thus the question.

It created one EXE file, I deleted the old one first, and that was the output. Would the best method just be for me to package the EXE into an Installer which will automatically attach all required files rather than trying to hunt down additional files?

Are you sure you then transferrred the release binary to the other machine? They're created in different folders, "Debug" and "Release".

Very good point, I was looking in the wrong folder...

When I get a chance, I'll send over the correct file and try again.