which is the best design or architecture for developing small windows apps using c#?
-
Hi , Let me make myself clear something first before proceeding with this post I don't want to create any new architecture or framework or design pattern. I want to make use of the existing tools and come up with a poc. Now let me explain the problem statement Requirement:- to build a windows app Technologies and database used:- Visual studio express edition 2008/ C#/ winforms or WPF/ sql server compact edition/if it is a multi use application SQL server Express edition will be used The application will be very simple with not more than 20screens. The underlying database will contain not more that 25tables. Even if it is a multiuser application the number of user will not be more than 5 at a time. The application will be used by a large number of people so bug fixing and introducing new features should be a breeze. The app will be having basic CRUD screens and the Business logic involved will not be too complex. To achieve this even if a Learning curve is involved it is acceptable. The time to market of the resultant should be very less. I want to develop the app for the above scenario. My goal is to develop a application with minimum number of lines of code. I Binged and found a lot of results like to use N-hibernate for ORMapping/or use Microsoft Enterprise library/Prism framework etc., I would like to know which framework or design pattern should I use to achieve the above functionality with least coding. I don't want to go with any third party tools. Pointers would be welcome. I want to develop and give it to the open source community as a POC for fast and effective programming for small scale applications.
-
Hi , Let me make myself clear something first before proceeding with this post I don't want to create any new architecture or framework or design pattern. I want to make use of the existing tools and come up with a poc. Now let me explain the problem statement Requirement:- to build a windows app Technologies and database used:- Visual studio express edition 2008/ C#/ winforms or WPF/ sql server compact edition/if it is a multi use application SQL server Express edition will be used The application will be very simple with not more than 20screens. The underlying database will contain not more that 25tables. Even if it is a multiuser application the number of user will not be more than 5 at a time. The application will be used by a large number of people so bug fixing and introducing new features should be a breeze. The app will be having basic CRUD screens and the Business logic involved will not be too complex. To achieve this even if a Learning curve is involved it is acceptable. The time to market of the resultant should be very less. I want to develop the app for the above scenario. My goal is to develop a application with minimum number of lines of code. I Binged and found a lot of results like to use N-hibernate for ORMapping/or use Microsoft Enterprise library/Prism framework etc., I would like to know which framework or design pattern should I use to achieve the above functionality with least coding. I don't want to go with any third party tools. Pointers would be welcome. I want to develop and give it to the open source community as a POC for fast and effective programming for small scale applications.
Try some of the articles here on Code Project on the subject of MVP/MVVM patterns. See also the answers to the question below.
jarajeshwaran wrote:
My goal is to develop a application with minimum number of lines of code.
I'm not sure how you would achieve this unless you are a super-coder.
-
Hi , Let me make myself clear something first before proceeding with this post I don't want to create any new architecture or framework or design pattern. I want to make use of the existing tools and come up with a poc. Now let me explain the problem statement Requirement:- to build a windows app Technologies and database used:- Visual studio express edition 2008/ C#/ winforms or WPF/ sql server compact edition/if it is a multi use application SQL server Express edition will be used The application will be very simple with not more than 20screens. The underlying database will contain not more that 25tables. Even if it is a multiuser application the number of user will not be more than 5 at a time. The application will be used by a large number of people so bug fixing and introducing new features should be a breeze. The app will be having basic CRUD screens and the Business logic involved will not be too complex. To achieve this even if a Learning curve is involved it is acceptable. The time to market of the resultant should be very less. I want to develop the app for the above scenario. My goal is to develop a application with minimum number of lines of code. I Binged and found a lot of results like to use N-hibernate for ORMapping/or use Microsoft Enterprise library/Prism framework etc., I would like to know which framework or design pattern should I use to achieve the above functionality with least coding. I don't want to go with any third party tools. Pointers would be welcome. I want to develop and give it to the open source community as a POC for fast and effective programming for small scale applications.
jarajeshwaran wrote:
The application will be very simple with not more than 20screens. The underlying database will contain not more that 25tables.
That doesn't add up; I'd expect a "list"-form and a "details"-form for every entity, allowing you to browse the entire collection or edit a single entity.
jarajeshwaran wrote:
Even if it is a multiuser application the number of user will not be more than 5 at a time. The application will be used by a large number of people so bug fixing and introducing new features should be a breeze
New features could be introduced with a plugin-system, you could opt to load an assembly dynamic. There are some articles on CP explaining how to do such a thing :)
jarajeshwaran wrote:
The app will be having basic CRUD screens and the Business logic involved will not be too complex.
So a generic CRUD-form would suffice?
jarajeshwaran wrote:
The time to market of the resultant should be very less.
I'd walk away as soon as this sentence drops, without any hesitation. The TTM should [b]never[/b] be confined by the manager. Imagine you selling a house with a limited TTM: would you sell it without a roof? --edit-- As I've been told, the houses are sometimes already sold before the drawings are even agreed upon. There seem to be special constructions to ensure that you get a roof. And that construction won't grind to a halt midterm.
jarajeshwaran wrote:
I would like to know which framework or design pattern should I use to achieve the above functionality with least coding. I don't want to go with any third party tools.
The .NET framework, and databinding :)
I are Troll :)
modified on Friday, September 18, 2009 4:09 PM