Friday, December 21, 2007

Code Signing Your VFP EXEs

John Robbins has a great post on why and how to digitally sign your EXEs. As he mentions, this is very important, especially on Windows Vista, if you want to have a professional looking application.

I've been using code signing for most of this year. We actually not only sign our application's EXE but also the installer so the user doesn't get the "unknown publisher" dialog when they install it.

10 comments:

Rick Schummer said...

Do you have problems with the VFP run-time DLLs not being signed?

Doug Hennig said...

No, because they aren't run as an EXE would be.

brucek said...

Hi Doug, do you have to install anything inside visual foxpro 9 to do this ? thanks.

Doug Hennig said...

Hi Bruce.

No, there's nothing to do from a VFP point-of-view; it's all handled at the operating system level.

Doug

Scott said...

Doug, I signed my vfp9 exe ok but by vfp 6 exe did not, can I assume that the vfp6 exe is not the correct format for signing?

Doug Hennig said...

I haven't tried a VFP 6 EXE but can't think of why it wouldn't work.

Scott said...

Doug

After signing a VFP6 EXE the exe launches to the "DO" dialog.

Doug Hennig said...

Sorry, I have no idea what the issue is.

Scott said...

Just FYI Doug...no solution needed.

Scott said...

Doug, I can say that signtool did not break the VFP 6 EXE, but it did break the way VFPR6.DLL can read it. If I run the signed VFP6 EXE in VFP9 using the DO command it runs, in VFP6 however it says "Not a Visual FoxPro EXE". So the long and short of this is DO NOT SIGN VFP6 exes and expect them to work in VFP6. End of story.