Geeks With Blogs

News
live stats

Domain Name Free Service
Get a free domain name like www.YourName.co.nr with the following features included: free URL redirection with cloaking, path forwarding, all meta-tags supported, kill-frame feature, NO forced ADS at all, and more.


Google




All content © Manish Agrawal
The content on this site represents my own personal opinions and thoughts at the time of posting, and does not reflect those of my employer's in any way.
Disclaimer:- All postings in this blog is provided "AS IS" with no warranties, and confers no rights.
Manish Agrawal My Experiments with Technology..

Narendra has written a good post on resolving the problem related to Digitally Signing of Assemblies is .Net 2.0
(url : http://geekswithblogs.net/narent/archive/2006/02/15/69536.aspx)

The problem is:

1. To digitally sign assemblies “AssemblyIncludeSigningInformation” must be set to true, but once it is set to true
   it becomes mandatory to write “AssemblyDelaySign” attribute in AssemblyInfo.cs file.
2. There is a logical error in the code (of AssemblyInfoTask.cs), which is mentioned by Narendra in the post.

For any user it will become a problem in case assembly is to be digitally signed.
As no where it is mentioned that DelaySign Attribute must be added in the AssemblyInfo.cs file and also how the
AssemblyDelaySign value must be given (i.e. it should not be left blank).
For e.g. this is an incorrect entry [assembly: AssemblyDelaySign()]

If the incorrect entry is given, it will get converted to [assembly: AssemblyDelaySign(“false”)]
which will further lead to error in compilation.

Where as Correct Entry must be: [assembly: AssemblyDelaySign(false)]

Posted on Monday, February 20, 2006 6:54 PM Build / Release | Back to top


Comments on this post: Problem with Digitally Signing Assemblies...

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Manish Agrawal | Powered by: GeeksWithBlogs.net