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.
Posts
Photo of the Day
12 hours ago
11 comments:
Do you have problems with the VFP run-time DLLs not being signed?
No, because they aren't run as an EXE would be.
Hi Doug, do you have to install anything inside visual foxpro 9 to do this ? thanks.
Hi Bruce.
No, there's nothing to do from a VFP point-of-view; it's all handled at the operating system level.
Doug
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?
I haven't tried a VFP 6 EXE but can't think of why it wouldn't work.
Doug
After signing a VFP6 EXE the exe launches to the "DO" dialog.
Sorry, I have no idea what the issue is.
Just FYI Doug...no solution needed.
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.
just fell on your post, as I was trying to sign VFP6 exe... so no way to sign them it looks.... damned !
I thought it was low level so without any issue...
I wonder that since 2007 there is no solution...
Post a Comment