Desktop application guidelines.

Question

0.00/5 (No votes)

See more:

Hi All,

I'm going to develop a desktop application in C# .Net with SqlServer. Give me some guidelines to start the project. Is it better to use 3 tier architecture? or 2 tier? What are the primary things that I need to take care before starting the project?

EDIT : I suppose to do a database application in C# . Net with SQLServer 2008. It is a small project contains about 50 forms. I'm going to use 3 tier architecture.

Posted 18-Dec-11 17:39pm

Silju MC

Updated 6-Feb-18 3:02am

v3

Add a Solution

2 solutions

Solution 1

Your question isn't answerable beyond one thing since you've given no details at all about what the application is supposed to do. That one thing? Do a very thorough job gathering the applciation requirements.

Posted 18-Dec-11 17:48pm

Dave Kreskowiak

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-12-18T17:59:00

The question is too broad to answer is any practically useful way. What would be the name of such article? I guess "The Universal Method of Programming of Everything in All Kinds of Desktop Applications". The choice between 1-tier (hardly an option if you want to use SQL Server :-)), 2-tier and 3-tier totally depends on your requirements.

You really should start with gathering requirements, formalizing them, description and analysis of use cases, then general architectural sketch and analysis, before you come to further decisions. You need to come through inception phase in development; and the results of this phase may outline your architecture. If you have no clue how to approach this phase, maybe you need to choose 0-tier architecture? :-)

At the same time, don't get me wrong: I don't want to say "read some books of software development methods before you start". Rather, I would advise to get some practice in development of some affordable projects all by yourself and learn some lessons from this experience. When you have a feeling of the process and learn from your (very likely) mistakes, you will really understand the books on methods and technologies. Or, should I say, you will hardly understand them very well before you get some essential practice in architecture, design and development.

—SA