UIP Application Block

[MadDruid]

Hi all,
i'm starting a new project and i'll have to switch to 3.5 framework.
I see that "The User Interface Process Application Block" is still in
version 2.0 and i like to know if it is no more supported and, in this
case, what new feature is replacing it.

Thanks,
Alessandro.

 

[Gregory Beamer]

The UIP is an MVC implementation. As such, I would look at ASP.NET MVC as
the "replacement" for the block. ASP.NET MVC is still in beta, but is
supposed to be RTMed by the end of the year (Hansleman mentioned it would be
released in a month ending in "ber" earlier in the year):

http://www.asp.net/mvc/

 

[bruce barker]

while UIP and MVC both use the MVC pattern, they have different purposes.

UIP was designed to separate the UI layer from processing logic and
allowed it to be replaced at runtime (factory model). your app could be
winforms or webbased. there was also a lot of work in persistence (to
hide the stateless of web applications). It also had CRUD support for
the model. but UIP is a dead end.

MVC was designed to bring the MVC pattern to web based applications on
asp.net. Its designed to stateless rather than statefull. It does have
navigation (routing), and the views are replaceable via a factory, but
are always send a web request to the controller. MVC is more comparable
to structs, but is modeling itself off of ruby on rails (especially if
you use ruby or python instead of C#). because javascript is much more
dynamic than C#, MVC is moving the dynamic nature of ROR to the client
side.

-- bruce (sqlwork.com)

 

[Gregory Beamer]

ASP.NET MVC is a very nice implementation, as long as one puts the main
logic into class libraries, which is the aim of the UIP. If done this way,
both can be adopted to a variety of UIs, as you are just using MVC to marry
facade bits to the page.

I agree that the UIP is not the way to go. ;-)