(Interestingly, the buggy Web Forms MVP code has been there since 15 Dec 2009. It just took some other interactions and some reasonable load to light it up.)

Breaking changes:

You’re now totally responsible for registering your presenters in the Windsor kernel. We don’t do it for you anymore. (Krzysztof Kozmic, the core Castle Windsor maintainer said auto-registration is generally a bad idea anyway.) If we try to resolve a presenter and you haven’t registered it, Castle’s exception will just bubble up and crash your page.

WebFormsMvp.Castle.MvpPresenterKernel has been renamed to WebFormsMvp.Castle.CastlePresenterFactory to a) make it consistent with how the other integrations are named and b) further emphasise the breaking API change.

Sorry everyone!

Reviews for this release

NuGet Oh great so I am forced to download Unity 2.0 yet again and then have all the project references changed to the newly downloaded ones.
Whats wrong with the ones I downloaded months ago and share with all my projects.
NuGet more like flaming NannieGet.
by cmonstoke
on Jun 7, 2012 at 6:14 AM

Issue with NuGet shouldn't be criticism to the framework itself. You can always get latest source and compile Unity adapter with latest assemblies. I found it is very powerful. It's additive(Option to evolve existing project). Surprisingly with its size, it takes care of a lot of development burden for you. Other MVP frameworks I've used left me alone after huge demand on structure change upfront.
by waveyus
on Dec 27, 2011 at 4:34 PM