Does Application Application Process (UIP) use Application Block before promises?
I am working on a project that needs to create an application that works as both a standalone application and a web application. We will consider using the Application Application Process (UIP) Application Block , which is available on the Microsoft Patterns and Practices website .
The application block claims that it can make this possible:
This block is a reusable code component that builds on the capabilities of the Microsoft .NET Framework to help you create both Web Forms and Windows Forms applications.
Before we devote too much time to further research, I'm wondering if anyone has experience using the UIP Application Box to build Web Forms and Windows Forms applications. How successfully have you separated the business logic from the UI logic when using UIP?
source to share
I am currently working on a project with UIP. I won't say it badly because I haven't actually invested more than a day. But let me express one feeling: On Saturday, my friends drink beer. I am in the office, struggling to use it and reading about 50 pages of documentation. The web.config application for the application is huge due to the number of nodes it uses. I am really, really sad, and even I love Microsoft and programming because thanks to them I have a job to pay the rent ... I'm really upset right now. And I'm usually a very happy guy.
I would rather use Aspnet MVC, cleaner, newer and built in with community input.
Hope it helps.
source to share
I used UIP to create an insurance claim application a few years ago. I found that he added complexity without any real benefit.
The UIP is not meant to keep your business logic and user interface separate. The goal is to allow you to reuse UI logic for asp.net and winforms. In practice, this doesn't work very well because desktop apps and web apps are two completely different animals.
I've also experienced quite a few errors related to session state on the asp.net side (I can't remember the details, sorry). In the end it hurt me that he removed all the UIP related code from the web app. After that, I made the code much easier to understand and debug.
If you're looking for a way to keep your user interface separate from your business logic, you should check out CSLA.net.
source to share
UIP really sucked, I had terrible experience using this. If you want a good example of architecture, you are after downloading the Northwind Starter Kit .
It shows the use of different endpoint / DB access methods (SQL Server / Access / NHibernate) and different interfaces (ASP.NET MVC / Monorail / Windows Forms / WPF).
He also has a related book , Archiving Applications for the Enterprise.
source to share