>>>>>>>>>>Have you ever thought about trying MVC out?
>>>>>>>>>
>>>>>>>>>What does MVC stand for?
>>>>>>>>
>>>>>>>>Model View Controller - one of the latest paradigms in ASP.NET programming
>>>>>>>
>>>>>>>I know I should not be writing this message but it is very frustrating when you bud in into a conversation without much (or any knowledge) on the topic. Mike Cole made a suggestion to Michel I was hoping that he would explain more on the topic of MVC and its benefits from his experience. But you had to bud in, I suppose, just to show that you know what the acronym stands for. Now Mike probably feels that you "took over" and being a gentleman is not "interrupting". Maybe I am the only one on this forum that feel that way but this is not the first time you do that and it aggravates the hell out of me. I hope you take this message as a constructive input <g>.
>>>>>>
>>>>>>
>>>>>>If you ask me, if anyone deserves flaming is Mike for throwing acronyms as if everyone should know them.
>>>>>
>>>>>Flame away. You would be foolish for doing so, though.
>>>>
>>>>I think Hugo was joking. But truly I would love if someone explained to me (like I am 6 yo) in two paragraphs what MVC is all about.
>>>
>>>MVC stands for Model-View-Controller. Instead of a URL pointing at a page which runs the hoopla and populates itself, a URL instead points at a Controller (pretty much just a method) that does the processing and returns a View (the page). The Model is your data representation. It doesn't rely on ASP.NET WebForm staples such as PostBack and ViewState and adheres to more standard web practices.
>>>
>>>MVC is well liked by software craftsmen because it is easier to unit test, it provides a better separation of concerns, it doesn't rely on Microsoft's HTML generation, and it runs lighter and faster than traditional WebForms. I would HIGHLY recommend checking it out if you are interested in web development. I can provide resources if requested.
>>
>>Thank you for taking the time to explain. I will to read more in details to really get it. But a follow up question. Does MVC apply to WinForm or WPF as well? or only to web-based applications?
>
>MVC is an architecture that has been around for 10 years or more. The implementation in .NET is for ASP.NET only as far as I know, not WinForms or WPF.

Thanks. Since I am mostly working (a little) in WinForms and plan for WPF, this will be one more technology I won't be learning <g>.