search

fxl31 / mybatisnet

Automatically exported from code.google.com/p/mybatisnet
0 stars 0 forks source link

Error configuring DAO while using Ibatis latest versions in VS2010 and running Unit tests in VS2010 #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What version of the MyBatis.NET are you using?
1.9.2

Please describe the problem.  Unit tests are best!

I'm fairly new to iBATIS and I seem to have hit a wall that I can't get around.

I keep getting the error message "Error configuring DAO. Cause: Ambiguous
match found", when I try to run my unit tests. Following are the points.

1.  Recently the solution has been converted from VS2008 to VS2010.
2.  All the projects are running with target framework of 3.5. So the 
application is running fine with the ibatis. If I change the target framework 
to 4.0 then I will be facing the same issue.
3.  As unit test projects uses frame work 4.0 by default and cannot be changed 
to any other framework, when I run the unit test which accesses the ibatis 
giving “Error Configuring DAO. Cause: Ambiguous match found”. It seems 
DynamicProxy exception. 
4.  I also tried the same by creating the  project in vs2010 with latest Ibatis 
version dll’s.

Is there any new version released which works with VS2010 (4.0). Please help me 
out. 

What is the expected output? What do you see instead?

It should run with out ambigious error.

Please provide any additional information below.

Create a new Web project in VS2010. create new web page and add this page as 
default. Add gridview control to the aspx page.
Write necessary code to get the data from DB using Ibatis.
Use the below versions
Ibatis DataAccess 1.9.2
Ibatis Data Mapper 1.6.2.

Original issue reported on code.google.com by phanikum...@gmail.com on 30 Jul 2010 at 1:37

GoogleCodeExporter commented 9 years ago 
This issue stopped my work and not able to continue. Only solution for me now 
is to revert back to VS2008. and Note that this is High priority.

Original comment by phanikum...@gmail.com on 30 Jul 2010 at 1:40

GoogleCodeExporter commented 9 years ago 
I have this problem too.But you can modify the compile property as .net 
framework3.5 to fix it temporary.

Original comment by nabbermei@gmail.com on 3 Nov 2010 at 12:11