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 Boris,
the issue can't come from the GAC, because NDO 1.2 uses the version number 1.2 for all NDO dll's while NDO 1.1 uses the version number 1.1.
But there is a registry key common for both versions:
HKEY_LOCAL_MACHINE\SOFTWARE\text & talk GmbH\NDO\1.1
In this key there is a value AddInPath which should point to the provider directory of the 1.1 version (these providers work with NDO 1.2 too).
The next matter is about ILAsm and ILDasm. The VS environment should be that way, that VS2003/NDO 1.1 should only find ILAsm/ILDasm 1.1.x.x and VS2005/NDO 1.2 should only find ILAsm/ILDasm 2.0.x.x. So you have to set the PATH environment variable according to this requirements.
To avoid a lot of preparation I'd suggest to put the less frequently NDO version into a virtual machine.
Best Regards:Mirko