Excellent, I'll look into that. Thanks.
Jason -----Original Message----- From: Aaron Hursman [mailto:[EMAIL PROTECTED] Sent: February 2, 2006 3:02 PM To: [email protected]; [email protected] Subject: RE: Error configuring DAO. Cause: Ambiguous match found. in my enviroment (vs.net 2005, asp.net 2.0, dataaccess 1.7 beta, datamapper 1.3 beta), i was having this problem, too. it was because: 1) the declaration portions of some of my configuration files (dao.config, sqlmap.config, sqlmap.xml, ...) was using the old syntax, and 2) i was using an older version of the castle.dynamicproxy.dll. make sure 1) the tops of those config files match the new syntax defined in the documentation for the beta versions of datamapper and dataaccess, and 2) you use the newest version of castle.dynamicproxy.dll. ________________________________ From: Jason Taylor [mailto:[EMAIL PROTECTED] Sent: Tue 1/31/06 03:01 PM To: [email protected] Subject: RE: Error configuring DAO. Cause: Ambiguous match found. The plot has taken a sudden turn. It seems to depend on which version of NUnit I'm using as to whether or not the test will fail: Compiled in VS2005, tested using NUnit for .NET 2.0 = fail Compiled in VS2003, tested using NUnit for .NET 2.0 = fail Compiled in VS2003, tested using NUnit for .NET 1.1 = success ! The constant seems to be NUnit for .NET 2.0. Has anyone else encountered trouble with NUnit for .NET 2.0? Thanks, Jason -----Original Message----- From: Chad Humphries [mailto:[EMAIL PROTECTED] Sent: January 31, 2006 2:27 PM To: [email protected]; [EMAIL PROTECTED] Subject: Re: Error configuring DAO. Cause: Ambiguous match found. Jason, I've been using iBatis in .NET 2.0 (the 1.x build) with no issues so far. If you are able to replicate the issue on a smaller scale (test project, test case) please post it to the list, I would love to look at it and see if I can replicate it. -Chad On 1/31/06, Jason Taylor <[EMAIL PROTECTED]> wrote: > Hello everyone, > > I have solved my problem regarding the ambiguous match issue; in short I was > using VS 2005 instead of VS 2003. > > When I recreated my project in VS 2003 everything worked fine. > > I imagine this has been asked before, but what, if any, support for the .NET > Framework 2.0 is planned? > > Any insight on the particulars of this 'ambiguous match' issue would be > welcome as well. > > Thanks again, > > Jason > > >
