>>>>Which of the two design patterns, MVC or MVP, is better suitable for ASP.NET web application?
>>>>
>>>>TIA.
>>>
>>>As I look for a good (newbie) article on MVC implementation (Googling all over the place) I see references to MVC, MVC 2, and MVC 3. I thought that MVC is just a concept (like OOP) and not a framework. Was I mistaken and MVC is a framework developed by Microsoft that undergone some version changes? TIA for clarifying.
>>
>>In VS2010 you can pick an MVC template when starting a new web project, so there is some framework in place.
>>
>>I haven't found it very useful so far. I still build web applications the standard ASP.NET way so.
>
>But you must be using some kind of logic (call it a pattern) when building your web application. I have also built a couple of ASP.NET applications but I suspect that if anybody who has a background in the computer sciences were to look at my design they would have a heart attack <g>. So I am trying to learn the correct (or better) approach. Mainly to separate the UI from the code in some kind of pattern. This is what I thought MVC does.
>Thank you.

Logic?

I don't need no steeenking logic!

I'm sure academic types would have a stroke looking at my code, but I find I can roll out reasonably extensible and easy to read code w/o any formal design pattern, and I can do it in a hurry.