M
Murray
Regarding the MS tutorial:
Using the COM Add-in Shim Solution to Deploy Managed COM Add-ins in
Office XP
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/htm
l/odc_comshim.asp
I have tried to get this example working several times, on several machines.
The result is that after the project is installed and MS Word 2002 is
launched, I am asked to trust my test certificate bound to the unmanaged
shim, but the managed VB.Net code does not run. If word is shut down and
restarted, I am not asked to trust the certificate regardless of whether I
chose to always trust the issuer or not.
The only departures from the tutorial I have made are:
1. I have generated a test certificate, and bound it to the unmanaged
shim as described in the article Digital Code Signing Step-by-Step Guide
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmarttag
/html/odc_dcss.asp). I assume test certificates are OK.
2. I have instructed the setup project not to build the shim or managed
add-in, as this removes the certificate attached to the shim earlier.
3. I have tried this tutorial with auto-generated interops, and with the
Office XP PIAs.
Any advice will be very much appreciated. Even some assurance that managed
code can be trusted in office would keep me sane...
Cheer
Murray
Using the COM Add-in Shim Solution to Deploy Managed COM Add-ins in
Office XP
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/htm
l/odc_comshim.asp
I have tried to get this example working several times, on several machines.
The result is that after the project is installed and MS Word 2002 is
launched, I am asked to trust my test certificate bound to the unmanaged
shim, but the managed VB.Net code does not run. If word is shut down and
restarted, I am not asked to trust the certificate regardless of whether I
chose to always trust the issuer or not.
The only departures from the tutorial I have made are:
1. I have generated a test certificate, and bound it to the unmanaged
shim as described in the article Digital Code Signing Step-by-Step Guide
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmarttag
/html/odc_dcss.asp). I assume test certificates are OK.
2. I have instructed the setup project not to build the shim or managed
add-in, as this removes the certificate attached to the shim earlier.
3. I have tried this tutorial with auto-generated interops, and with the
Office XP PIAs.
Any advice will be very much appreciated. Even some assurance that managed
code can be trusted in office would keep me sane...
Cheer
Murray