Sunday, February 05, 2012
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 Tobias,
I guess, that id.ToString() is a string which can't be recognized as a valid expression by NDO or the underlying ADO.NET provider. Try to do the following:
NDOQuery<...> q = new NDOQuery<...>(this.persistenceManager, qh.systemComponentId + "= {0}", false);q.Parameters.Add(id); // id must have the same type as systemComponentId
If that doesn't help, please write a small test solution and send it to me.
Regards:Mirko
we try to include as much as possible diagnostic code into NDO but we can't cover all situations with it. NDO relies heavily on the .NET base class libraries, which tend to return null or throw NullReference exceptions. All you can do is debugging as usual. Something is causing an object to be null and we have to discover, what it is. I'll send a version of the NDO.dll to your email address which shows the readable names of the methods in which the exception occurs. Run the code with the dll and send the name of the method to me.
Best RegardsMirko