Thursday, September 09, 2010
Support » Support Forum
Register Login
HomeWhat is NDO?- Executive Overview- NDO for DevelopersHow NDO Works- Persistent Classes- Mapping- Queries- Reverse Engineering- Inheritance, Polymorphism- Distributed ApplicationsLicensingSupport- Support Forum- FAQ- Solutions- Downloads- E-Mail Support- Tutorial VideosOnline ShopContact
Welcome to the NDO support forum!
Please register/login at the site if you want to post a thread. We sometimes copy support mails of common interest to the forum. They appear with anonymous sender. Please post your messages in English language if possible. You can do your posts also in German, we will translate your post and our answer so that all users of the forum can read your posts. The forum software requires that javascript is enabled. Please do not insert licence information or licence keys in forum posts. If you know a good answer to a post of another user, feel free to reply! The forum is monitored. We reserve the right to remove posts we consider not to be useful for other forum users.
Hi Falk,
per default NDO searches the NDOMapping.xml in the directory where the executable resides. In case of the shadow copy this is the shadow copy directory which doesn't contain the NDOMapping.xml.
The workaround is to provide the mapping file path to the PersistenceManager constructor. I suggest writing a factory class with a static method:
public class PmFactory{ public static PersistenceManager Create() { return new PersistenceManager("PathToYourMappingFile"); }}
In your tests use PersistenceManager pm = PmFactory.Create();
If you make a change to the PmFactory.Create method, it will apply to all tests.
I suggest using the TestDriven.NET add-in for visual studio. With this add-in you can run tests from inside the VS editor and seeing the result in the output pane.
I suggest also to write a little test runner program, which references your test dll and is able to run a single test for debugging purposes.
Best Regards:Mirko