This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I have recently returned to working on a solution taht uses Lightspeed 2.2. The solution is using a relatively old nightly build (2.2.1149.11463) which at the time addressed an issue we were having with DynamicData. However, another issue was recently discovered. It appears that in this build, the FirstOrDefault() Linq method was not populating child collections, even if they were marked as EagerLoad. I downloaded the latest nightly build and this fixed the problem. However, DynamicData now appears to be broken. When the application first fires up, I get the following exception raised: Type : System.NullReferenceException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : Object reference not set to an instance of an object. And when I try to fire up a Dynamic data maintenance screen, the following exception is raised: Type : System.Web.HttpException, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a Message : The file '/DataMaintenance/OrganisationTypes/ListDetails.aspx' does not exist. Given that I haven't been working with Lightspeed 2.2. for a while, has something changed that I am now missing? I have resolved my initial problem by using the SingleOrDefault() Linq method, which is quite valid for my current situation, but am likely to have occasions where I will need the FirstOrDefault option.
Thanks, Mark |
|
|
Thanks for reporting this. We have made some changes in this area since the build you had before and it looks like those changes are not working with your model. Is it possible for you to post your model (just the .cs file) to help us reproduce this problem? Thanks! |
|
|
Hello Mark, Thanks for providing the model. It seems we had a problem handling to-one association properties when they were declared in the partial class and not backed by an EntityHolder. I've committed a fix for this and it will be included in nightly builds dated 8 Dec 2009 and above. |
|