I would go with Castle - it might be lacking in Documentation (which is worthwhile if it is up to date) but it has a good mailing list (http://groups.google.com/group/castle-project-users) plus pretty wide adoption within the Alt.Net community.
On Sun, Jan 17, 2010 at 12:48 PM, Boris Berak <[email protected]> wrote: > Hey all, > > I'm about to embark on a new .NET project and require some advice. I > am unfamiliar with both the Castle and Spring.NET frameworks as no > such framework has historically been used at my current workplace. > However, I feel that adopting a framework of some kind will be the > best option considering the small amount of resources that I can > allocate to this new project. > > An overview of the project would be: > > - MySQL db > - Data access layer (considering Subsonic 2.2 or 3, or NHibernate if I > choose to go with Castle) > - WCF services layer > - ASP.NET MVC 2 front end > > Googling 'castle vs spring.net' brought up the usual pros and cons for > both sides (and this question may also do the same - a good thing). > From what I gather, it seems that Spring.NET requires more > configuration but has a lot more documentation than Castle. > > Based on the small amount of information I have made available, can > anyone advise on which framework will be more suitable? If anyone also > has any information about the learning curve and general experience of > using either framework I would love to hear it (although I'm not too > fussed about burying my head in the books). > > Thanks in advance! >
