RE: [aus-dotnet] Thoughts on the User Interface Process Application Block

[Brett Errington]

Using it now in an enterprise application

 

And I would like to point out it is not as easy as they make it out to be. That being said I think its worthwhile implementing in any medium to large application. Just be aware of a number of the issues it has:

 

·         Web frames are not supported by default so implementation is a bit of pain.

·         There are issues with the back button in web forms (although there is patch).

·         I find the documentation unfriendly and unfinished.

·         There are a few others I can’t remember off-hand.

 

Its advantages:

 

• Separating process logic from GUI and user interaction.
• Navigation isn’t hard-coded into the application (but rather resides in the .config file).
• Reusability.
• Ability to switch between windows / web applications with relative ease.
• Relatively straight forward approach to allowing users to “pause” a task and resume it later (or have other users resume it instead therefore providing a small workflow engine).

 

You should keep an eye on the following forum which is probably the best source for technical information / problems:

http://www.gotdotnet.com/Community/MessageBoard/MessageBoard.aspx?id=3733

 

HTH

- Brett 

---

From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of Nick Zdunic
Sent: Wednesday, 7 July 2004 10:35 AM
To: dotnet@xxxxxxxxxxx
Subject: [aus-dotnet] Thoughts on the User Interface Process Application Block

 

I'm looking for thoughts or real experience of this application block which is an implementation of MVC and more.  Version 2.0 was released in April.

 

Any thoughts on how easy/difficult it is to use.

 

Any thoughts on the advantages gained from it.