I agree that learning on a small project is a better approach. But as you say "a small MVC app using EF" which implies that I need to know some basics about EF. And so far, I can't get my mind around it (EF). Or - probably more honest answer - didn't spend uninterrupted time learning.
Thank you.
>No. By default, MVC uses EF, but it's not required.
>
>However, rather than just jumping into EF, I'd take a learn-as-you-go approach. Figure out how to do a small MVC app using EF, then start digging into details of MVC or EF as needed.
>
>
>>Thank you very much for your input on model bining in Web Forms. I have not looked at TypeScript or CoffeeScrip and do not really what these technologies are all about. But the bottom line you are strongly suggesting ASP.NET MVC; correct? Not the first time, of course. In this case, if I were to go the ASP.NET MVC route, first I need to learn Entity Framework. Which I started and then never finished. :(.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
