Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Sep 30, 2011 10:36 AM by DarrellNorton
Sep 29, 2011 03:37 PM|LINK
We’re starting a new application and wanted to get suggestions/recommendations/opinions on which technologies, frameworks, patterns, etc. to use. We would like to choose these items so that they’re relevant now and will still be relevant and not abandoned
in the future.
We know we’re going to use a layered application with a presentation layer, maybe a service layer, a business layer, a data layer, and a cross-cutting concerns “layer.” We’re planning on the “good” architecture stuff of loose coupling, separation of concerns,
dependency injection, etc., etc.
The application will be an Intranet-based web site using Windows authentication, running on IIS, SQL Server database, all layers running on the same server, and using ASP.NET. We also need to support multiple clients, that is, the normal web browser interface
(this is the main app ui), a Silverlight interface, and eventually a mobile app interface.
So, our questions aren’t about specific details but rather more general:
Sep 30, 2011 10:36 AM|LINK
Check out the Microsoft Application Architecture Guide 2.0: http://msdn.microsoft.com/en-us/library/ff650706.aspx
It shows you, for a given layer, the Microsoft technologies/frameworks and some patterns. Here is the Presentation Layer chapter for example:
Here is the Presentation Layer technology matrix: http://msdn.microsoft.com/en-us/library/ee658088.aspx
And here is the "Designing Rich Internet Applications" chapter: http://msdn.microsoft.com/en-us/library/ee658083.aspx