Strongly naming the Microsoft Enterprise Library
I suppose you have tried the Enterprise Library from Microsoft. You probably also used it in a project that should be strongly named. Seems like the compiled DLL's in Eneterprise Library are not Strongly named! Well, the intention is that, as long as the source code is shipped with Enterprise Library, the DLL's are not Strongly named. You have to do it yourself. Fair enough, and the solution is described in Tom Hollander's blog:
http://blogs.msdn.com/tomholl/archive/2005/04/05/405764.aspx
If you still can't figure it out, here are the gory details:
http://blogs.msdn.com/tomholl/archive/2005/12/02/499529.aspx#502110
No comments yet.
Leave a comment
Search
Knut Hamang
This is the official site for Knut Hamang. I am a professional technical consultant specialized in Microsoft and .NET technologies and platforms. I work as an independent consultant in Norway and have more than 10 years of professional experience. To get in contact with me, please send me an email or check my public profile on 
Recent Posts
Recent Comments
- Yoteadviertoportero.Wordpress.Com on Using log4net in Web Applications – a real-life example
- Raj on Using log4net in Web Applications – a real-life example
- onitsuka tiger mexico 66 black/mazarine on Working with Visual Studio 2005 and ADO.NET
- reviews on Working with Visual Studio 2005 and ADO.NET
- RamS on Working with Visual Studio 2005 and ADO.NET