-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 
Author Message
 Post subject: Recompile break strong name
PostPosted: Wed Nov 08, 2006 4:38 pm 
Newbie

Joined: Wed Nov 08, 2006 4:31 pm
Posts: 1
I need to recompile nHibernate to use Log4Net version 1.0.2.10. I was able to recompile without problem however other component using nHibernate stop working because the strong name were different. When I recompiled with the new version of Log4Net I also sign the nHibernate dll as mentioned in the download section. However, this result in a different public key token. Is is possible for me to recompile and sign but to keep the old public key (154fdcb44c4484fc)?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 08, 2006 10:28 pm 
Senior
Senior

Joined: Sat Mar 25, 2006 9:16 am
Posts: 150
Use a binding redirect in your app.config or web.config


Top
 Profile  
 
 Post subject:
PostPosted: Thu Nov 09, 2006 3:15 am 
Contributor
Contributor

Joined: Wed May 11, 2005 4:59 pm
Posts: 1766
Location: Prague, Czech Republic
No, it's not possible. As grennis suggested, you can use a binding redirect in the application configuration file, by keeping the original NHibernate but specifying that log4net 1.2.10 should be used instead of 1.2.9.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.