Billy McCafferty

S#arp Architecture 0.7 represents a major upgrade to the infrastructure of S#arp Architecture - but the overall architecture, with respect to application layering, remains the same.  This release is far simpler to work with than previous versions while still providing plenty of flexibility.  A huge thanks goes out to Frank Laub who has provided terrific feedback and guidance on making S#arp Architecture simpler while using it on real-world web applications.  This release's many changes include:

• NHibernate 2.0 Beta 1 integration is now included.
• Integration with Spring.NET has been dropped. Spring.NET is a fantastic library with world class AOP, IoC support, and many other modules. But for S#arp Architecture, a simpler approach was found for performing dependency injection without the need for external configuration files. If you're still in need of many of Spring.NET's terrific libraries, you'll want to take a look at release 0.6.* which comes preconfigured with Spring.NET.
• The ~/SpringConfig folder no longer exists
• There is no more SpringInteropController
• The Spring XML generator has been dropped from ProjectBase
• GenericDAO now uses the native NHibernate session.
• HTTP Modules are no longer needed to support the Open-Session-in-View pattern for NHibernate session management.
• All configuration, such as the DB connection string, is now just within web.config.
• Concrete types needed for Dependency injection are now declared at the top of each dependency interface; e.g., IOrderDao.
• NHibernate session storage mechanisms, for both web and unit-tests/winforms have been added to ProjectBase.Data and ProjectBase.Web.
• The Identity attribute has been renamed to DomainSignature to better reflect its purpose.
• Controllers now simply inherit from the base MVC Controller.
• ProjectBase.Web.ControllerFactory has been introduced with built in dependency injection.

I'm confident you'll be very pleased with the changes and would highly recommend upgrading your project if you're already using this framework and do not need the many powerful utilities found within Spring.NET.

http://www.codeplex.com/SharpArchitecture

Billy McCafferty