Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Architecture> UI Architecture
 

Pages: 1
Architecture
UI Architecture
Page:1/1 

  Print all messages in this thread  
Poster Message
mohamed
User



Location:
Salmia, kuwait
Joined on:
10-Mar-2008 19:55:21
Posted:
136 posts
# Posted on: 10-Jun-2010 12:44:27.  
Hi,
One of the senior developers is proposing the following architecture for a big winforms application we are working on (the old VB6 version had 700 forms!!)

The application has 3 logical tiers, DAL (by LLBL), BL, and the WinUI

The proposal is to build each winform in its own project/dll. This means we will end up with almost 700 dlls for the project's forms.

The goal behind this architecture is to ease and speed development.

I would appreciate hearing any feedback for or against such a design?
  Top
psandler
User



Location:
Chicago, IL
Joined on:
22-Feb-2005 22:24:13
Posted:
540 posts
# Posted on: 10-Jun-2010 15:27:39.  
I would start with trying to understand the claim that it would "ease and speed development". I actually can't imagine any justification for taking this approach.

One big downside--the solution file would be unmanageable. You could have a trimmed- down version of it for daily use, but then any changes to the BL would have to be checked against all UI projects to make sure everything still compiles.



My C#/SQL Blog (some LLBL content)
Email: psandler70 (at) yahoo.com
 
Top
MTrinder
User



Location:
London by day, Milton Keynes by night.
Joined on:
08-Oct-2008 17:55:47
Posted:
1461 posts
# Posted on: 10-Jun-2010 17:27:40.  
It won't ease and speed development, it will make it more painful and slower. As well as the unmangeable solution file, there is also the build time to be considered - there is an overhead for each .dll that has to be built.

A much more sensible approach is to structure your UI projects into logical business groups - ie Customer forms, Product forms etc. Another approach is to use logical functional groups - list browsing forms, edit forms etc. Either of these is a much more manageable approach.


Matt
  Top
omar
User



Location:
Salmiya, Kuwait
Joined on:
15-Oct-2004 15:44:57
Posted:
569 posts
# Posted on: 15-Jun-2010 23:41:24.  
thanks for your feedback

The an other goal that he mention behind that architecture is to ease to do updates for customer by sending the modified dll . as updates could be either daily or weekly.




We don't know who we are until we see what we can do  Top
MTrinder
User



Location:
London by day, Milton Keynes by night.
Joined on:
08-Oct-2008 17:55:47
Posted:
1461 posts
# Posted on: 16-Jun-2010 18:08:30.  
How is it any easier to send a customer 1 dll from 700, rather than 1 from dozen or so ?

And you shouldn't be updating customer systems in this manner anyway - build a proper installer and get them to update their installation. Otherwise it is way too easy to lose track of which version of your application they are using.

Matt
  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.