Sign in
 
Microsoft Developer Network > Forums Home > Archived Forums Forums > Acropolis > MVC Pattern, Architectural Design, WPF & Acropolis?
Ask a questionAsk a question
Search Forums:
 

QuestionMVC Pattern, Architectural Design, WPF & Acropolis?

  • Thursday, September 06, 2007 10:58 AMvalko Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

    Hi,

     

    Long time ago in Enterprise Library 1.1 there was library called UIPAB, and it was supporting MVC pattern perfectly.

     

    Unfortunately UIPAB is missing from Enterprise Library version 2.0 and its latest version is on .NET 1.1 :-(

     

    My question is is there any chance we will have a proper MVC in WPF in the future .NET 3.5?

     

    I don't like usual asp.net code behind approach, because you cannot reuse the controller for other, non-asp page based views.

     

    Moreover, classes that are tightly coupled to asp pages are very difficult to test which should be one of the goals of the MVC pattern. Of course one can develop custom classes to implement MVC, but I would like to have more structured and standard approach for such important part of the application like UI - ideally something in WPF or at least part of Enterprise Library.

     

    Actually my question is connected with real world problem. We successfully migrated a lot of 1.1 business applications on .net 2.0, and started some migrations for classic asp 3.0 to asp.net 2.0

     

    We would like to plan our future migrations to WF and WCF as well and we need some approach for UI. As I told you code-behind do not seems good option - it has very low reusability and it will be very hard to use it on different platforms.

     

    I would highly appreciate any help or information about MVC or any other more structured approach for thin cross-browser client we need.

     

    Or maybe Acropolis Client Application Framework supports creation of thin cross-browser and I just missed it??

     

    It is really frustrating - .net farmework exists from ,ore then 7 years and we still do not have proper UI with clear separation between the view and the controller, common Microsoft guys, get a grip. All foundations are excelent way to go, but without fast simple thin cross-browser UI how we will connect to WF nad WCF?

     

    Is there any conspiracy here :-)

     

    thank you

     

       

All Replies