Printable View
To sign or not to sign... At this point I am wondering why did I sign sign apps that I develop for internal use only. I am seriously considering removing it because of the confusion over expired certificates. Test certificates are only good for a year (why?).
If I do remove it I know that the app has to be reinstalled, but that is the only drawback I have seen so far.
Just seeking some thoughts or experiences.
Yeah, why DID you sign internal apps?
I signed an app that is mostly used for internal use, but it is published (just internal and to a few cooperators) and has periodic updates. I'm not sure that you can do that without signing. The certificates are a pain anyways. If you are trying to be cheap, there is some means to sign it for longer than a year without buying a certificate, because I have....I think, but no matter what you do, you will forget how to do it by the next time it becomes an issue. I keep a file around with steps. Unfortunately, that file wasn't started early enough, so I'm not quite sure where I got the certificate from, or how I made it. I think I DID make it, cause I vaguely remember going through a whole bunch of steps to make a 10 year certificate, but I just don't quite remember, and the notes I took don't start early enough.
These apps are used by many people internally, so I am wondering what the above means. Are you saying that the updates won't happen? Wonder if that is why I DID? ;)Quote:
Originally Posted by Shaggy Hiker
It was so many years ago that I can't currently remember what the point was. Somebody else will probably know. The updating feature of a ClickOnce application is nice. Why I signed it....that I can't recall. I assume that I at least thought I had to, or else I certainly wouldn't have.