19. December 2010 07:37
It has been quite some time since our last release. This latest release brings upgrades in several dependencies as well as removing of others.
The following dependencies have been upgraded to their latest versions:
The following have been removed from the project:
- MvcContrib.Castle -> There were only two classes from this assembly we were using: WindsorExtensions.cs and WindsorControllerFactory.cs. Since the release schedules of many OSS projects do not match up and the fact that the MvcContrib project had already updated their vNext (MVC 3) branch with the castle dependencies and not the MVC 2 branch, it was decided we should bring these two classes in and lose the dependency when it was not needed.
- Castle.DynamicProxy2 and Castle.MicroKernal -> The assemblies were merged into other assemblies by the Castle project. They are no longer needed
- NHibernate.Linq -> Since NHibernate 3.0 GA has a new Linq provider, it was no longer needed.
Download it now
We are offering this release in two formats, a Templify package and binaries only. Since the source is readily available, we no longer will be prodiving it in the downloads. If you do not know what Templify is, you can read about it here. If you are going to spin up a new solution, please follow the guide for using Templify below. It will show you how to get the package into your Templify repo. If you are wanting to upgrade a 1.5.x or higher solution, follow the guide to upgrading.
Starting a fresh solution with Templify
If you have not already downloaded and installed Templify, do so now. You can obtain the build from: http://opensource.endjin.com/templify/download.htm
- Download the Sharp Architecture 184.108.40.206 Templify package from: https://github.com/downloads/sharparchitecture/Sharp-Architecture/sharp-architecture-220.127.116.11-templify-package.zip
- Extract the contents into their own folder
- run the copy-package.cmd script
- Follow the instructions located here (http://weblogs.asp.net/alecwhittington/archive/2010/10/10/using-templify-to-create-a-new-s-arp-architecture-solution.aspx) to get up and going using Templify.
Upgrading your existing project
These instructions are only good for people using Sharp Architecture 1.5.x or higher.
- Download the Sharp Architecture 18.104.22.168 binaries only zip from: https://github.com/downloads/sharparchitecture/Sharp-Architecture/sharp-architecture-22.214.171.124-binaries-only.zip
- Extract the contents into their own folder
- copy the contents of the folder into your /lib folder
- Delete the following from the /lib folder
- Castle.DynamicProxy2.dll and .xml
- Castle.MicroKernel.dll and .xml
- MvcContrib.Castle.dll and .xml
- Open your solution in Visual Studio
- Go through each project and remove references to
- Now you need to update your projects to use the proper version of the updated components. There are several ways to do this, from upgrading each .*proj file manually or by using Visual Studi. I've done it both ways, but prefer to use VS to help out.
- Using Visual Studio - Open a project that references any of the following: Castle.*, NHibernate.*, MvcContrib.*, Fluent NHibernate, or SharpArch. Right click on the reference and click properties. Once there, set Specific Version = true. This will update the proj file to use the version that is in your /lib folder.
- Build the solution to see what errors are there
- Remove reference to MvcContrib.Castle from your global.asax in the .Web project.
- [OPTIONAL] Update your component registration to use the newer Castle.Windsor API
Your mileage will vary. If you find any issues with this, please report them on the google group, http://groups.google.com/group/sharp-architecture.
I would like to point out that we have removed the dependency on MvcContrib.Castle, if you are using anything more than the WindsorExtensions.cs and WindsorControllerFactory.cs, then you will need to implement that functionality yourself or upgrade MvcContrib to the latest dependencies. While we normally do not like to nick code from others, in this case we wanted to upgrade to the latest version of Castle (also required for NHibernate and Fluent Nhibernate) and would have had to make a custom build of MvcContrib to do so properly. The end result is that those two classes now reside within S# and we have one less dependency that has a dependency.
11. October 2010 06:14
Now that we have published our 2.0 road map, several people have asked us how are we going to get there. Simple, one step at a time.
One step at a time
We have previously blogged about Templify (here and here) being the way we are going to deliver a S#arp Architecture solution. That was step one for us, so you could say that we are already starting to deliver 2.0. Our next steps will be as follows (subject to change)
- Create an initial 2.0 release that includes (v1.7.X)
- Convert solution and projects to Visual Studio 2010
- Convert all projects to .NET 4.0
- Reorganize the solution structure for the solution template (moving to a Who Can Help Me based folder structure)
- Solution to use new MSBUILD based build system
- Package for Templify
- Document new Build process
- Add documents for Templify
- Create next release that includes (v1.8.X)
- LINQ Specifications
- Component composition
- Component registration
- Isolate NHibernate
- Create the next release (v1.8.5.X)
- Support for Castle 2.5
- Support for NH 3.0 (whether it is a GA release or not)
- Fluent NHiberate compiled against NH 3.0
- Support for MVC 3
- Change Validation (Data Annotations for UI, NHibernate.Validator for Model)
- Create the next release (v1.9.X)
- Convert Default Package to use Spark as its default view engine
- Add documentation (blogs and wiki) on how to properly setup the Spark environment
- Include the new Plugin architecture
- Add documentation (blogs and wiki) on the new Plugin architecture
- Support for NoRM / MongoDb
- Support for Azure
- Create the 2.0 release (v2.0.X)
- Final bug fixes
- Update all documentation
- Add samples via Blog posts
- Update Northwind
- Update Who Can Help Me
- Start creation of 3rd sample
All of this is subject to change based on the needs of the community / the team.
As you can see, we have an ambitious schedule a head of us. The team and I are really excited about what we have planned and cannot wait to share it with everyone. Some of it is very exciting, like the Plugin architecture and alternate data store support.
S#arp Architecture 1.6.5 will be the last stable release until 2.0 is released. The interim releases will all be listed as Alphas or Betas and should only be used in production if YOU are comfortable with it. If you are not or need to wait for a stable release, please wait for 2.0. For each release, we will also provide another Templify package. If you want the full source, you can download it from GitHub.
10. October 2010 18:51
Last week Howard van Rooijen blogged about Templify. I am happy to announce that Templify is now the offical way to create a S#arp Architecture solution. Templify comes packaged with a S#arp Architecture package, so there is nothing you need to do, other than install Templify, to get it going. I'll leave the details on how to install and use Templify for Howard's post. This article assumes you have Templify installed already.
Create a new S#arp Architecture solution with Templify.
7. October 2010 23:44
For Sharp Architecture v2.0 one of the problems the development team was very keen to solve was the problems end users have getting started with Sharp Architecture.
Visual Studio Templates, T4 code generation files, dropping custom DLLs in particular folders etc... all of these steps are painful for the end user and painful for the development team as the majority of the support requests on the discussion group are about environmental set-up problems - these are the most time consuming and difficult problems to solve - they are also a time sponge that prevents the team from devoting time to making Sharp Architecture a better product.
A few weeks ago I started working on a new deployment mechanism for Sharp Architecture - once I had a working prototype it soon became apparent that the scope of this tool far exceeded just Sharp Architecture as it could be used as a generic template and packaging tool - so we made the decision to split it off into it's own OSS project.
So without further ado - let me introduce you to Templify.