Digital Signing of Code for Outlook Script

[Guest]

I have a VBA script that I have signed in Outlook with my own DS and I am exporting it to a common file location on a local network. I want others on the network to be able to import it into an Outlook session and run it without having to set security to low or having to sign the code themselves with their own DS. But when I have a user test it, the script is ingored unless he/she chages the security setting for Outlook. There is no indication that the script is even recognized as being signed. I don't know whether the problem is with the users machine recognizing my DS or whether deploying a signed script for use in Outlook is not supported. All I can find in browsing FAQs is how to individually sign a script for use in Outlook using the selfcert program. Nothing about how to deploy a signed script. Any help would be appreciated. Thanks

AlWitNoHumor

 

[Sue Mosher [MVP-Outlook]]

Outlook VBA code isn't meant to be deployed at all. It's for your own
personal use. Someone else would need to import it and then, if desired,
sign their own VbaProject.otm file.

A better solution would be to build and deploy a COM add-in.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

I have a VBA script that I have signed in Outlook with my own DS and I am

exporting it to a common file location on a local network. I want others on
the network to be able to import it into an Outlook session and run it
without having to set security to low or having to sign the code themselves
with their own DS. But when I have a user test it, the script is ingored
unless he/she chages the security setting for Outlook. There is no
indication that the script is even recognized as being signed. I don't know
whether the problem is with the users machine recognizing my DS or whether
deploying a signed script for use in Outlook is not supported. All I can
find in browsing FAQs is how to individually sign a script for use in
Outlook using the selfcert program. Nothing about how to deploy a signed
script. Any help would be appreciated. Thanks.

 

[Guest]

Sue, thats what I was afraid you were going to say. I got the impression from my research that it was not supported, but I never found anything that came right out and said that I couldn't do it. It used to be fun to write simple (localized) solutions using Office Automation Code, but those were the good ol days, before the evil ones starting exploiting holes in MS security and before MS decided to fix the problem by breaking the back of its own automation products. Thanks

----- Sue Mosher [MVP-Outlook] wrote: ----

Outlook VBA code isn't meant to be deployed at all. It's for your ow
personal use. Someone else would need to import it and then, if desired
sign their own VbaProject.otm file

A better solution would be to build and deploy a COM add-in

--
Sue Mosher, Outlook MV
Author o
Microsoft Outlook Programming - Jumpstart fo
Administrators, Power Users, and Developer
http://www.outlookcode.com/jumpstart.asp

I have a VBA script that I have signed in Outlook with my own DS and I a

exporting it to a common file location on a local network. I want others o
the network to be able to import it into an Outlook session and run i
without having to set security to low or having to sign the code themselve
with their own DS. But when I have a user test it, the script is ingore
unless he/she chages the security setting for Outlook. There is n
indication that the script is even recognized as being signed. I don't kno
whether the problem is with the users machine recognizing my DS or whethe
deploying a signed script for use in Outlook is not supported. All I ca
find in browsing FAQs is how to individually sign a script for use i
Outlook using the selfcert program. Nothing about how to deploy a signe
script. Any help would be appreciated. Thanks