Hiya Have you tried a binding redirect in your configuration file... the same issue arises with regard to NHibernate, and is answered in this forum posting.
http://forum.springframework.net/viewtopic.php?p=827&highlight=#827 On a related issue, there is no particularly compelling reason for Spring.NET using the version of Log4Net that it does. This issue has come up a few times on the Spring.NET mailing list, and on the forum, so in the interests of just keeping everything simple (it is only logging), I daresay we (Spring.NET) could synch up our versions of Log4Net with both iBatis.NET and NHibernate (or vice versa). I'll ping the rest of the Spring.NET team (actually, I'll just forward this to our list). Ciao Rick > ---------- Forwarded message ---------- > From: Hai Hoang <[EMAIL PROTECTED]> > To: [email protected] > Date: Wed, 31 Aug 2005 09:41:51 -0700 (PDT) > Subject: ibatis used dated log4net dll > Apc.Test.Persistence.ApplicationDaoTest.TestGetAllApplications > : System.TypeInitializationException : The type > initializer for > "IBatisNet.DataAccess.Configuration.DomDaoManagerBuilder" > threw an exception. > ----> System.IO.FileLoadException : The located > assembly's manifest definition with name 'log4net' > does not match the assembly reference. > > I am using ibatis.net with spring.net and both project > uses different version of log4net. do you know who to > fix this without download the source code and compile > it?
