By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,165 Members | 1,916 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,165 IT Pros & Developers. It's quick & easy.

Signing ClickOnce Manifests and Shared Assemblies

P: n/a
I am trying to understand the difference between signing ClickOnce manifests
and signing shared assemblies. My company is building .Net 2005 WinForm
applications for internal company use only. Currently, the ClickOnce security
settings on the applications is set for "Full Trust". We are using shared
assemblies across development groups, but none of these assemblies are signed
with strong names since signing assemblies is only required when installing
libraries to the GAC,which is something we are not doing. (All of our
applications contain the necessary DLL's in their SmartCient package, no need
for the GAC)

Right now we are having an issue when publishing our applications.
Currently, we disabled signing CLickOnce manifest from Visual Studio. But
every time we publish from VC, this feature automatically enables itself. Is
it a requirement to always sign the ClickOnce manifests? And if so, I would
like to use a single certificate for this purpose across all development
groups so that everyone is using the same certificate.

Overall, we want to avoid signing and using certificates as much as possible
because all of our .net application are internal and fully-trusted by end

Jul 14 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.