Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 09, 2013 01:54 PM by DigiMortal
Feb 08, 2013 08:14 AM|LINK
Actually I am about to start a web-application using c#, .net 3.5 and Sqlserver 2008.
I already know what is opps, 3-tier architecture etc.. (As I am a self taught man, whatever I know about MS Technologies).
I need to develop it in a proffesional manner, like what it should be used from MS technology. I never planned for an architecture before, yes I developed web application before, but never approach architecture and design patterns.
So I request to you, please guide me from where I should start so it'd be like a mannered web-application
Feb 08, 2013 09:50 AM|LINK
Feb 08, 2013 09:58 AM|LINK
You might want to look up resources such as the 'Microsoft Application Architecture Guide v2' or 'Microsoft .NET - Architecting Applications for the Enterprise' by Dino Esposito and Andrea Saltarello and then decide what kind of architecture best fits your
Who are the target users of your application? You might accordingly decide on the kind of user interface you may develop, the QoS requirements you want our application to fulfill, and so on.
Feb 08, 2013 10:01 AM|LINK
Using the factory pattern you can designed the architecture well and good.
Feb 08, 2013 11:20 AM|LINK
However please be aware that there is no 'one size fits all' solution. Apply a pattern only if you feel it is applicable to your context. Maybe the Gurus on this forum (I am not one of them!) can help you better if you share more specifics of your application.
Feb 09, 2013 01:54 PM|LINK
As a first thing I suggest you to read some books that also stop on architecture. My suggestion is Microsoft®
.NET: Architecting Applications for the Enterprise (Pro-Developer) by Dino Esposito. You can also take some more complex and harder to read books (I'm sure somebody will recommend you some of these) but the one I suggested is good to get started. It's
somewhere between theory and practice and it is good start to more complex books.
To get started I suggest you to start building some application and then also take a look at how other developers have built UI-s and data layers of their applications, how they have managed dependency injection and testability etc. Learn as you go. With
no hands-on practice it's hard to make valid decisions.