MVC2 with MVVM over LINQ to SQL classes

I'm adding a ViewModels subfolder to an MVC2 solution for the partial classes and metadata classes that proxy my LINQ to SQL classes (which are in the Models folder). Unfortunately, the ViewModels namespace makes the partial classes no longer map to their Models class counterparts...

I'm keeping my 'service' or 'repository' classes that provide unit testable data access methods in the Models folder.

I can imagine taking the contents of the Models folder to a WCF web service in the future ~

I'd rather not have a seperate set of classes for the ViewModels to proxy the Model classes, but maybe I'm just being lazy.

How else would you go about it?

I'm being lazy. Seperation of concerns tells me so... 

The metadata classes should fit over the ViewModel classes.

The ViewModel classes will proxy the Model classes so that the Model classes can live in a web service.

JohnAskew said:

I'm being lazy. Seperation of concerns tells me so... 

 

The metadata classes should fit over the ViewModel classes.

The ViewModel classes will proxy the Model classes so that the Model classes can live in a web service.

 

I'd use something like RIA services or anything that can automatically keep the classes in sync.

You will have to have a seperate .dll for your model should you require WCF because you will need to strip your classes of the impurity that Linq to SQL has for creating classes (and EF < 4.0).

In order to use Linq to SQL with WCF you will need to strip your classes to simple POCO objects that you can send as messages across the wire. Since Linq to SQL lacks any change tracking, this is the only option, otherwise things will not work at all on the client end, especially when you use WCF to generate your proxy classes. If you are using dastasets (and don't need to support non .NET clients like Java) then they ae OK as they have their own change tracking if not a bit chunky.

If you are using Visual Studio 2010 then you can use Linq with the new change tracking feature in entity framework 4. This also enables a best practice of creating a seperate .dll with your Model (and .edmx), that you can re-use, instead of the tightly coupled model that you have at present.

PaoloM said:

JohnAskew said:

*snip*

I'd use something like RIA services or anything that can automatically keep the classes in sync.

RIA is going to simply things a heck of a lot for sure, it is pretty good, and should fit MVC without issue

PaoloM said:

JohnAskew said:

*snip*

I'd use something like RIA services or anything that can automatically keep the classes in sync.

Thanks, Paolo.

http://www.silverlight.net/getstarted/riaservices/

I'd put ViewModels behind the Silverlight pages instead of just using the code-behind files, but I like these tools!

http://www.silverlight.net/learn/videos/all/net-ria-services-intro/

VS2010 design support !     -  where have I been? Thanks again.

http://www.silverlight.net/learn/videos/all/ria-services-support-visual-studio-2010/

vesuvius said:

PaoloM said:

*snip*

RIA is going to simply things a heck of a lot for sure, it is pretty good, and should fit MVC without issue

Looks like RIA will address all the issues you pointed out I confront with my original post. Thanks, volcanoMan.

edit: besides seperating the Model into a DLL of POCO. Gratis.