D
droid44
I have developed an application that is being installed in various different
countries, it is developed in 2000 and then I build both a 2000 mde and a
2003 mde with a VB.net launcher to run the correct file based on the Access
version installed.
The 2003 mde is digitally signed using a Verisign class 3 code signing
certificate.
A lot of users have Office 2003 and 80% of them run without any problem at
all however on some machines it pops up with the message saying the code has
been signed by '...' and asks if they want to trust it and then as soon as
they tick to trust it and click ok they get the message 'security settings
restrict access to the file because it is not digitally signed'. When you
look at the list of trusted publishers on the machine we are listed and the
certificate shows in the certificate store.
The mde includes a reference to an 'Amyuni PDF Creator' dll and the program
uses the mscomm Activex control (although this is not in the references).
Verisign told me to use the signcode.exe utility to digitally sign the dll
files but this has not helped.
I build the install using Installshield 11 Express and this handles the
registering of the dlls on the end users system.
Any ideas would be most appreciated...
countries, it is developed in 2000 and then I build both a 2000 mde and a
2003 mde with a VB.net launcher to run the correct file based on the Access
version installed.
The 2003 mde is digitally signed using a Verisign class 3 code signing
certificate.
A lot of users have Office 2003 and 80% of them run without any problem at
all however on some machines it pops up with the message saying the code has
been signed by '...' and asks if they want to trust it and then as soon as
they tick to trust it and click ok they get the message 'security settings
restrict access to the file because it is not digitally signed'. When you
look at the list of trusted publishers on the machine we are listed and the
certificate shows in the certificate store.
The mde includes a reference to an 'Amyuni PDF Creator' dll and the program
uses the mscomm Activex control (although this is not in the references).
Verisign told me to use the signcode.exe utility to digitally sign the dll
files but this has not helped.
I build the install using Installshield 11 Express and this handles the
registering of the dlls on the end users system.
Any ideas would be most appreciated...