Click here to Skip to main content
15,878,048 members
Please Sign up or sign in to vote.
1.00/5 (3 votes)
See more:
Quote:
we are designing windows form project using dot net frame work.
What are best way to develop interface and its architecture eg.
DML operation, reports etc.


What I have tried:

we have ADO .net stored procedure, quires, web service and telerik
Posted
Updated 13-Dec-19 7:02am

The question is far too broad for a Quick Answers forum. Google is the best place to find architecture and design papers.
 
Share this answer
 
We can't answer that, it's far too broad a subject, and we would need a lot more information about what your project is intended to do, and what market sector it is going into (many of them will have their own rules, regulations, and standards which must be adhered to). Since you also mention "web service" you will also likely have to work within relevant legislation such as GDPR as well.

Start with Google, and work out from there.
 
Share this answer
 
Comments
Tahir Mahmood From karachi 15-Dec-19 23:36pm    
we are designing ERP, it is windows form application, if we thin our lots of time spend on design UI of any form, we are finding easy to create UI like MVC when we provid table UI create automatically.
It is highly subjective topic and there is no right or wrong way in software development. As suggested by other folks you should do some brainstorming over the topic and get clarity about what problems your application is going to solve, what it is intended to do, its target audiences, input/output, liability on 3rd party services etc.

However, as a starter I would say following things. But, take it with the grain of salt. It is very subjective topic.

If your application is going to be developed as a stand alone windows application then it can be considered as monolithic app. You can use layered architecture in that case.

Create layers for your application as follows
1. Data Layer:- consist of your data CRUD operation
2. Business Layer : Consist of your domain/model classes
3. IOC Layer or DI layer: if you want to implement Dependency Injection
4. (if required) Facade/Proxy layer: to access database or 3rd party service, store info for time being in cache
5. Service layer: for internal data service that can be use
6. Unit test project
7. Main Project:
Views, ViewModels, HelperClasses etc


However, it all depends on what kind of application you are going to create.

You can find plenty of information on internet in respect of requirement.
 
Share this answer
 
v2
Comments
Tahir Mahmood From karachi 15-Dec-19 23:32pm    
what is the easy way to create UI by its model like MVC in windows form application?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900