Quote:
Originally Posted by HarryT
Getting a digital certificate to sign code with needn't be expensive.
|
No, it doesn't
have to be, but once it's
required what is to prevent them from
making it expensive? What about my own apps that I want to write and run on my own PC? Why should I have to get them signed?
I've run into this in Excel -- I have several spreadsheets I track things in, and I've written button launched macros to automate entering the data (I copy it from my source, then click the button to get the data entered and formatted correctly) — but guess what? That's right: Excel has a cow because the macros are stored in the file. I
finally figured out how to make my own certificate and sign them so that I can use them without turning off Excel's macro watch "feature," but it took me several
hours to track down and about another hour to actually make
work. For extra added fun, I'll probably have to do the same circus act
next time I want to do the same thing again, as I'm unlikely to remember what I did before ... assuming that it doesn't change in the meantime.
If they want stuff signed badly enough that they'll hassle their users about it, the least they can do is put a stinkin' entry in the stinkin'
help file that covers the topic, and make that entry easy to find, by, like, you know, cross-referencing it, and listing it in the stinkin'
index!
Sorry, but I find the matter a bit annoying.
