A signed executable file that was made with Visual FoxPro 6 or Visual FoxPro 7 does not run correctly (843594)
The information in this article applies to:
- Microsoft Visual FoxPro for Windows 7.0
- Microsoft Visual FoxPro for Windows 6.0
SUMMARYBecause security is an important consideration for many developers, signing executable files to validate their authenticity is becoming a general practice. Unfortunately, when an executable file is made with a version of Microsoft Visual FoxPro that is earlier than Visual FoxPro 8 and then that executable file is signed, the executable file no longer runs correctly.SYMPTOMSYou create an executable file by using Visual FoxPro 6 or Visual FoxPro 7. Then, this executable file is signed with a Software Publisher Certificate. When you run the signed executable file, a Do dialog box appears. The expected behavior is for the executable file to run.CAUSEWhen the executable file is signed, the following events occur: - The size of the file increases by the size of the certificate.
- The certificate is added to the end of the file.
- Some bytes from the EXE header are modified.
This problem occurs because Visual FoxPro makes some verifications when the application is loaded. Visual FoxPro looks for information that should be in a fixed position at the end of the file. However, because the signing process modifies the original file by adding the certificate at the end, Visual FoxPro cannot find this information any longer. Therefore, the dialog box that is described in the "Symptoms" section prompts you for this information. RESOLUTIONTo resolve this problem, upgrade to Microsoft Visual FoxPro version 8.0 or a later version, and recompile the custom executable in that version. When it is recompiled, the custom executable must be signed again with a Software Publisher Certificate.
Modification Type: | Major | Last Reviewed: | 3/9/2005 |
---|
Keywords: | kbCodeSnippet kbprb KB843594 kbAudDeveloper |
---|
|