Proxy object references in MVC code

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开发者_StackOverflow社区 types and have done with it ?

My personal feeling is to create an abstraction by creating a model and placing the Collection in that and referring to the collection in the UI code from the model.

but this seems to violate the DRY principle with respect to proxies.

Well, the best practice is to use a View Model which is populated from the Model. In many cases they could be the same because the view shows all the properties returned by the service, but another view could show only a subset of them. That's why having a view model is considered a good practice. This view model can also contain some calculated properties that are specific to the view. To further simplify the mapping between those objects you could use AutoMapper. There's also a nice article you may take a look at explaining the concept of view models.