MSDN has a priceless set of ASP.NET Security How-To Articles. Its a must read area for all web developers and developers having interest in application security.
Here is the link for all of you:
Microsoft Patterns & Practices Security How Tos
Enjoy!
Wow! Just another goodie!!
Look at this. Now a guidance explorer is available from the Patterns & Practices team at codeplex.com for all the people who want to better their performance. Congratulations to the team for the good work.
The guidance explorer let you explore the guidances mentioned in various patterns and practices guidelines. No more browsing through numerous web pages to find out the guidances. A neat tool with an file explorer style tree to keep the points tidy.
Just loved it. I shall request you all to get it installed and most importantly READ.
Have it in the following URL:
[http://www.codeplex.com/guidanceExplorer/Release/ProjectReleases.aspx?ReleaseId=9763]
Architectural patterns are meant for providing solutions to architectural problems in software engineering. It fundamentally provides a readymade structure of a solution that is targeted at a particular established proble. It describes a structural organization schema for a solution consisting of subsystems and underlines their responsibilities and interrelations.
However there is significant difference between the architectural pattern and the architecture itself. An architectural pattern is a concept that captures essential elements of a software architecture. The pattern is a guideline to implement a particular architecture. So following a particular architectural pattern, the architects may come out with several different and unique architectures. Of course they will carry some similar set of characteristics.
One way of depicting the same is that Architectural pattern is an abstraction (interface in .net?) and actual architectures are implementations of the same.
So how can we compare architectural patterns to design patterns? Architectural patterns are larger in scale and gives an overall structure of the solution. There might be several design patterns in a single architectural pattern.
Model View Controller is an Architectural pattern.
View: The user interface (GUI) or the software which produces User Interface (ASP.Net Web forms ) which enables display of information about the model to the user. Any object that needs information about the model needs to be a registered view with the model.
Example - Boundary Class
Controller: The user interface presented to the user to manipulate the application. User Driven Events in GUI.
Example - Control Class
Model: The core of the application. This maintains the state and data that the application represents. When significant changes occur in the model, it updates all of its views.
Example - Entity Class