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:
If you were starting this new application, what technologies, frameworks, and/or patterns would you use for the presentation layer?
If you were starting this new application, what technologies, frameworks, and/or patterns would you use for a service layer?
If you were starting this new application, what technologies, frameworks, and/or patterns would you use for the business layer?
If you were starting this new application, what technologies, frameworks, and/or patterns would you use for the data layer?
Would you choose ASP.NET MVC, Entity Framework, simple ADO.NET, SOA, WCF, Enterprise Library, etc., etc., or some non-Microsoft equivalent of some of the technologies?
g6temp
0 Points
1 Post
Technology/Framework/Pattern Suggestions for a New Application
Sep 29, 2011 03:37 PM|LINK
Hello.
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:
Thanks!
DarrellNorto...
All-Star
86665 Points
9634 Posts
Moderator
MVP
Re: Technology/Framework/Pattern Suggestions for a New Application
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:
http://msdn.microsoft.com/en-us/library/ee658081.aspx
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
Darrell Norton's Blog
Please click "Mark as Answer" if this helped you.