Dave Burke : Freelance .NET Web Developer specializing in Online Communities

ASP.NET Ajax and Community Server: Referenced Assembly Strong Names

We're starting to make progress integrating the ASP.NET Ajax Control Toolkit into Community Server when we...D'OH!...encounter "Assembly generation failed -- Referenced assembly CommunityServer.Components does not have a strong name."

We could generate strong names for CS.Components and any other reference assemblies or, heck, unsign the Toolkit assembly and remove the AjaxControlToolkit.snk key.  Next.


Comments (7) | Post RSS RSS comment feed

Posted on 5/28/2007 10:46:27 PM by Dave Burke
Categories: .NET | Community Server
Tags: no tags for this post

Related posts

Comments (7) -

5/29/2007 6:35:38 PM Permalink

PSSST!

The ASP.NET Ajax Control Toolkit should not be referencing any of the CS projects, it should only be consumed by them.  This will remove part of the problem of them not being signed.  However, signed DLLs can't be used by unsigned DLLs unless the signed DLL is compiled with the [assembly: AllowPartiallyTrustedCallers] attribute.  Just put it in the AssemblyInfo.cs file if it is not already there.

Beginners...   Tong

Bill Bosacker |

5/29/2007 7:05:13 PM Permalink

Good thing it's you who said that.  I'd have to punch out anyone else! Smile  Dude, I just know this works very sweetly.  The Toolkit HAS to reference the CS projects.  As I continue the series you will understand, Obi-Wan.

daveburke |

5/29/2007 7:39:04 PM Permalink

Ok, I'll wait and see.  BTW, are you making your custom control by deriving from a toolkit control and overriding properties/methods, or are you making changes to the toolkit itself and breaking the upgrade path?  *W*

BTW, I'm Yoda (all seeing), not Obi-wan.  Smile

Bill Bosacker |

5/29/2007 7:46:04 PM Permalink

An ASP.NET application with source code, the Toolkit is.  You duplicate and customize, or you do not.  There is no try.  

Upgrade path??????  Purists.

daveburke |

5/29/2007 8:36:38 PM Permalink

What reason for, the source code is?  New project, new namespace, copy & paste.

Padawans.

Bill Bosacker |

5/29/2007 9:49:35 PM Permalink

Once you fear starting down the dark path of modifying the Toolkit source, forever will it dominate your project, consume you it will.  Unless a CS Master like me you are, question you must.

daveburke |

5/29/2007 10:02:50 PM Permalink

Ok, new topic.  Calendar control is almost complete and will be released later this week.  Fixing the bugs that existed in the original control is taking longer than planned, plus I've improved a few things and added some new features.  I spent my entire Memorial Day weekend working on it, so I'm ready for a break.  Smile

Bill Bosacker |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke