My problem with MVC was/is that I just could not get my mind around the Entity Framework. And I need to have this app working - yesterday. So once I deliver this job I will take up on every EF course in Pluralsight and work on it.
>I'll second Craig's take. Just because MS show it in an example doesn't necessarily make it 'best practice' :-}
>
>>Good guess. Sor far I decided to leave the Form in the Site.Master and in the pages where I need the Form to use class "form-horizontal" to add this class using jQuery. It is very simple, just one line of code in the script section. But in the end if I see that I have to set this class for almost all forms I may as well set it right in the Site.Master.
>>Thank you.
>>
>>>My guess... to make it easier for the developer.
>>>
>>>>What bothers as far as removing Form element from the Site.Master is why Microsoft VS 2012 automatically adds Form element to the Site.Master. I am sure the designers of VS had to have a reason for it. Hence I am afraid to break something.
"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
