Proxy object references in MVC code

Posted by krystan honour on Stack Overflow See other posts from Stack Overflow or by krystan honour
Published on 2010-05-06T09:36:03Z Indexed on 2010/05/06 9:38 UTC
Read the original article Hit count: 228

Hi there,

I am just figuring out best practice with MVC now I have a project where we have chosen to use it in anger.

My question is.

If creating a list view which is bound to an IEnumerable is this bad practise?

Would it be better to seperate the code generated by the WCF Service reference into a datastructure which essentially holds the same data but abstracts further from the service, meaning that the UI is totally unaware of the service implementation beneath.

or do people just bind to the proxy object types and have done with it ?

My personal feeling is to create an abstraction but this seems to violate the DRY principle.

© Stack Overflow or respective owner

Related posts about asp.net-mvc

Related posts about asp.net-mvc-2