Have you made any changes to how the Id property is exposed?

Hello -

I just downloaded the latest nightly build, dated Oct 03.  The previous version I have been using is dated Sep 06.  I am using LS in a WCF service, and copying the Contracts and Model libraries to a directory where the client can reference them, so I'm basically shipping LS entities across the wire.

With the latest build, my client no longer can see the Id field.  I am reading all entities from a given table into a list, then using the Id property as an alias for the actual values stored in the entities.  For some reason, the Id property is no longer valid in my client.  This could be something else I botched up, I'm not above admitting that, but before I beat my head against the wall trying to find that, I thought I would ask.

So, have you guys changed anything with the visibility of the Id property?

Thanks, Dave

Nope, not as far as I can tell.  Besides, if your server can still see the Id property, and you're using the same library in the client and the server, then I don't think it can be a visibility issue.

One thing I have noticed in VS2010 is that if you are using the Client Profile, and reference a library that needs the full profile, it often doesn't give you a meaningful error like "If you need to reference X.dll, you need to upgrade to the full profile," but just silently fails to find members from base classes in the library that needs the full profile.  That could explain why you're seeing the properties defined in your Model assembly but not in the LightSpeed assembly.

Thanks for the quick reply.  I worked through all the Client Profile issues early on, so I don't think that's causing me problems now.

Back to bug hunting -- what in the #$%&(! did I do to mess things up this time??