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 am building an application that uses a WCF service as the data source for all clients, and the clients include ASP.NET MVC2 web server and several WinForms applications. I am tickled to death that you have improved things so that I don't need to use DTOs anymore -- even without using the distributed unit of work pattern, I get full-fledged entities across the wire to my client apps! However, I did notice you are still stripping/masking the ID of the entities before exposing them. I followed the arguments on why this was done, and how to get around it, as relates to DTOs. Now the question is, what do I need to do to get the ID at the client level under the new paradigm? Quite frankly, this doesn't even seem to be controversial. I get a list of entities from the service. Now I want to delete one, or get details on one -- MVC patterns are all predicated on using the ID to reference the record. So, is there a flag I can set to include the ID with the entities, or do I still need to do the partial class thing? Please advise, thank you Dave |
|
|
So, what happened guys? You all are usually right there with some kind of answer, but this post has been ignored completely. I really need to know how to handle this situation in the new beta, as the structure of how you do things has changed quite a bit without the DTO layer. Can I get some feedback please? Thanks, Dave |
|
|
OK, I'm either blind or an idiot, you can pick one. I found the Entity.Id property hiding in plain sight, and I am able to use it as I expected to.
Sorry for the vacuous post... |
|