I was talking to another list member off list, Chris Weisel, who was experiencing the same issues from after downloading the binaries from the website. He walked me through what he was doing and wrote a post that hasn't made it to the list yet. It should say something along the lines of: the binaries that are linked from ibatis.com (DataMapper-bin-1.2-Alpha.zip) ship with Castle 1.1.0 but the projects themselves were built against Castle 1.0.3. I've confirmed this with Reflector. Opening IBatisNet.DataMapper.dll or IBatisNet.DataAccess.dll and going to the Castle reference in the References tree node. You should see this:
// Assembly Reference Castle.DynamicProxy Version: 1.0.3.0 Name: Castle.DynamicProxy, Version=1.0.3.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc When you drag the Castle assembly (from the same .zip file into Reflector you see this: // Assembly Castle.DynamicProxy, Version 1.1.0.0 Name: Castle.DynamicProxy, Version=1.1.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc They're not the same :( I saw Gilles promoted the build to beta. I think we need to start the cycle again with 1.2.1 and 1.6.1. Chris also said that if you copy Castle 1.0.3 into your app's bin folder everything appears to work ok. - Ron --- Bob Hanson <[EMAIL PROTECTED]> wrote: > No matter what I do, I am unable to get rid of the error. > > Can someone please just tell me if I'll have any problems if I > continue to use castle.dynamicproxy 1.0.3 with mapper 1.2?
