Comments on: NDbUnit Refactored for Explicit Assembly Dependencies http://unhandled-exceptions.com/blog/index.php/2009/06/07/ndbunit-refactored-for-explicit-assembly-dependencies/ Miscellaneous musings on life, .NET development, and related things that don't really matter Thu, 17 May 2012 21:44:40 +0000 http://wordpress.org/?v=2.7 hourly 1 By: sbohlen http://unhandled-exceptions.com/blog/index.php/2009/06/07/ndbunit-refactored-for-explicit-assembly-dependencies/comment-page-1/#comment-26751 sbohlen Wed, 27 Jan 2010 22:15:13 +0000 http://unhandled-exceptions.com/blog/index.php/2009/06/07/ndbunit-refactored-for-explicit-assembly-dependencies/#comment-26751 @Frank: Assuming that you have the proper version of the libraries referenced, there should be no explicit dependency on NDbUnit.SqlClient.dll (so I cannot immediately see the reason for your error). If you are using the Proteus libraries from the Google Code site, can you please ensure that you are also referencing the NDbUnit.* assemblies that are in the Google Code download of the latest Proteus binaries ( http://proteusproject.googlecode.com/files/Proteus.Utility.UnitTest_1.2.5.34419.zip ) rather than either the older NDbUnit binaries from the screencast code downloads or the newer NDbUnit binaries from the NDbUnit Google Code site? Note that if you are applying these to an existing solution, you MUST do a CLEAN of the solution and then a complete REBUILD of the solution after updating the references as Visual Studio doesn't (always) consider a change in the version of a referenced binary to be a reason to rebuild a project and so its possible you have 'stale' / 'old' binaries in your bin/Debug folder(s). If you try this and it still doesn't work please try to get me a copy of the entire solution that evidences the problem and post it somewhere that I can get ahold of it (either post a ZIP file somewhere I can download or check the whole solution (binaries and all) into one of the free SVN hosts out there. Let me know how you make out. The behavior you're reporting should certainly NOT be true if you have the proper versions of the binaries referenced in your solution. -Steve B. @Frank:

Assuming that you have the proper version of the libraries referenced, there should be no explicit dependency on NDbUnit.SqlClient.dll (so I cannot immediately see the reason for your error).

If you are using the Proteus libraries from the Google Code site, can you please ensure that you are also referencing the NDbUnit.* assemblies that are in the Google Code download of the latest Proteus binaries ( http://proteusproject.googlecode.com/files/Proteus.Utility.UnitTest_1.2.5.34419.zip ) rather than either the older NDbUnit binaries from the screencast code downloads or the newer NDbUnit binaries from the NDbUnit Google Code site?

Note that if you are applying these to an existing solution, you MUST do a CLEAN of the solution and then a complete REBUILD of the solution after updating the references as Visual Studio doesn’t (always) consider a change in the version of a referenced binary to be a reason to rebuild a project and so its possible you have ’stale’ / ‘old’ binaries in your bin/Debug folder(s).

If you try this and it still doesn’t work please try to get me a copy of the entire solution that evidences the problem and post it somewhere that I can get ahold of it (either post a ZIP file somewhere I can download or check the whole solution (binaries and all) into one of the free SVN hosts out there.

Let me know how you make out. The behavior you’re reporting should certainly NOT be true if you have the proper versions of the binaries referenced in your solution.

-Steve B.

]]> By: Frank http://unhandled-exceptions.com/blog/index.php/2009/06/07/ndbunit-refactored-for-explicit-assembly-dependencies/comment-page-1/#comment-26749 Frank Wed, 27 Jan 2010 20:38:19 +0000 http://unhandled-exceptions.com/blog/index.php/2009/06/07/ndbunit-refactored-for-explicit-assembly-dependencies/#comment-26749 Hello Stephen, At the moment I am enyoing your great screencast Summer Of NHibernate. In session three you are doing some unittesting and for that you use a dll from Microsdesk. Since I am using a MySQl database I wanted to use the Proteus library for unittesting. So, as I found on this page, I added a reference to NDBUnit.MySQL.dll, NDbUnit.Core.dll and MySQL.Data.dll. I then created the methods the way you do in your screencast (including the dataset). If I then run the method "GetMyTestDataXMLFile" I recieve an error. See below: TestCase 'M:DataAccessLayerTest.NHibernateDataProviderTests.GetMyTestDataXMLFile' failed: Can't load assembly NDbUnit.SqlClient; ensure the assembly is located in the app binary directory or the GAC Why does it want to load the NDbUnit.SqlClient? Do you have any idea? I alse have the MbUnit.framework as a reference for the earlier tests. Thanks in advance. Frank Hello Stephen,

At the moment I am enyoing your great screencast Summer Of NHibernate. In session three you are doing some unittesting and for that you use a dll from Microsdesk. Since I am using a MySQl database I wanted to use the Proteus library for unittesting.
So, as I found on this page, I added a reference to NDBUnit.MySQL.dll, NDbUnit.Core.dll and MySQL.Data.dll. I then created the methods the way you do in your screencast (including the dataset).
If I then run the method “GetMyTestDataXMLFile” I recieve an error. See below:

TestCase ‘M:DataAccessLayerTest.NHibernateDataProviderTests.GetMyTestDataXMLFile’
failed: Can’t load assembly NDbUnit.SqlClient; ensure the assembly is located in the app binary directory or the GAC

Why does it want to load the NDbUnit.SqlClient? Do you have any idea? I alse have the MbUnit.framework as a reference for the earlier tests.

Thanks in advance.

Frank

]]>