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
|
Hello - I'm not sure when this stopped working but we just recently updated LightSpeed 4 to the 9/28 nightly build. We are using VS 2010 SP1 on Windows 7. Our solution is a Windows Forms client paired with a WCF service. We do not use distributed entities. What we do is reference the model DLL on the client side as well as the service side. It's quite possible we were never supposed to do this, but on the client side we were creating a new EntityCollection<> and adding new entities to it using the .AddRange method. After updating the Lightspeed libraries this quit working. No exception, no warning, it just did nothing. To fix it we changed from an EntityCollection<> to a List<> and it works as expected. This is not a crisis situation, we found an arguably better way to do what we wanted to do, but thought you should know. Thanks! Dave Newman |
|
|
|
|
Hi Dave, There has been a change in the behavior of the EntityCollection in the last couple of months where items will be added into a deferred list prior to the collection being marked as non lazy. We dont recommend using EntityCollection for adhoc collection management so I would definitely recommend switching over to a List<> based approach. See this thread for some other recent discussion on this :) http://www.mindscapehq.com/forums/thread/424162
|
|
|
|
|
Thanks, that explains a lot! I must have decided to use EntityCollection simply because it was a collection of Entities. Silly me :) |
|
|
|
