Creating Model Classes with LINQ to SQL

I posted sample code in C# for this video on my website

panjkov.qsh.eu/.../entry69.aspx

Thanks....

nice video, i would like to see C# version of code.

Thanks

Thanks Stephen.  One question regarding the repository pattern.  If your interface returns objects that are created by the Linq to SQL designer, aren't you tying your interface -- and by extension the controller -- to a Linq to Sql class?

Great Concept...

Great Video...

http://www.inti.ac.id

http://www.sansinosoftware.com

http://www.kchrysant.com

http://www.ktpasirindo.com

http://www.binaman.co.id

I hate to reiterate question hpinsley asked.

I guess that was not the point of this screen cast, but in real life scenario we would have to manually create object model and write code that populates it in repository.

The dependency Injection Pattern is very helpful, but I believe a Factory pattern provides greater flexibility in terms of code versioning and implementation of new IRepository...

Great Video...

Is there any difference in speed or performance between Method Syntax and Query Syntax?

Nice Video.  It would be nice to see how to get to another table besides a view of all.  That is, what if I want to return list 1.

It's nice to show an example of a pattern that lets me upgrade from linq to sql to linq to entities later (which is my plan)

really.. thanks for the great videos!

This is one of the best videos I have seen that shows all the MVC concept and how to code all it parts. I also like how you use notepad to give a list of what we will be doing. The only thing I might have added was an NUnit test with a MOCK IRepository to really round things out. Either way, it is still a great video

Thank you.

<script>alert('ok')</script>

more...........

Nice Video

thanks man :)

very useful (F)

great explanation. Thanks

Good set of vids so far .. MVC looks pretty badass

Thanks,MVC looks simple for decompeling

Here is the lambda expression in C#:

var movies = dataContext.Movies.Select((m) => m);