Then I would recommend the one with documentation (Spring.NET). ;) You see, when I was doing Java programming then, we were deciding which framework to use: Struts (which is complete with documentation, but a little bit complex to use) or Java Server Faces (which has a few or no documentation at all).
The reason why I would recommend Spring.NET is because there is an assurance that in case half-way through your project completion you run into some issues/problems, you can always consult your documentation. Contrast this with no documentation at all: you would have to tinker with that technology or desperately seek out solutions from forums/groups online. Regards, Benj On Jan 17, 8: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!
