On Windsor 3.2 release

Wind­sor 3.2 release is now live on nuget and source­forge.

This release is mostly about bug­fixes and incre­men­tal improve­ments and while some break­ing changes were made, for vast major­ity of users this will be a drop-in update.

The high­lights of the release are in the doc­u­men­ta­tion, so I won't repeat them here.

End of an era

It is the last release to sup­port .NET 3.5 and Silverlight.

Also, I'm think­ing of sun­set­ting (such a nice word) Remot­ing facil­ity, Fac­tory Sup­port facil­ity (the one that allows you to spec­ify fac­tory method via XML, not to be con­fused with Typed Fac­tory facil­ity), Event Wiring facil­ity and Syn­chro­nize facility.

Obvi­ously, Wind­sor being a com­mu­nity dri­ven project, if some­one wants to step in and take over any of these facil­i­ties we'll keep updat­ing them. Oth­er­wise this will likely be their last release.

  • Pingback: The Morning Brew - Chris Alcock » The Morning Brew #1297

  • http://twitter.com/golan_a Adam Golan

    Krzysztof, what are the rea­sons for drop­ping those fea­tures (espe­cially Fac­tory Sup­port Facil­ity and Event Wiring facil­ity)? You con­sider them wrong in any way?
    Could you exm­plain why, if so (or if that's explained aready could you point to a link)?
    Also what's wrong with xml? Why did it fell out of favour? Every­body is using the flunet api for reg­is­tra­tion now? Still it seems like a good idea to have a mech­a­nism of con­fig­u­ra­tion that doesn't require recompiling…

  • Krzysztof Koźmic

    @twitter-211444660:disqus Noth­ing wrong with these facil­i­ties per se. It's just that they haven't seen much devel­op­ment lately, and they're not that widely used either, which makes the cost of keep­ing them up to date and releas­ing them rel­a­tively high com­pared to ben­e­fit they offer to the few that use them.

    Even if the facil­i­ties aren't going to be updated, they will likely still be work­ing just fine with future ver­sions of Wind­sor, and being open source and very small (in terms of code­base size) they're eas­ily adapt­able if a need arises.

    About XML, I've never been in favour of it to begin with. Speak­ing of fac­tory sup­port facil­ity the sort of func­tion­al­ity it pro­vides is code, not con­fig­u­ra­tion, so I actu­ally wouldn't put that in XML.