Krzysztof Koźmic's blog

Update: Due to a regres­sion error dis­cov­ered in Wind­sor Fac­tory Sup­port Facil­ity, we decided to act fast and pro­vide updated pack­age of Wind­sor, with­out the issue. Get it here. Sorry for the inconvenience.

What bet­ter way of start­ing a new year can there be, than fresh set of releases from Cas­tle Project?!

Core 1.2 (with more)

Cas­tle Core 1.2 has now its own, sep­a­rate pack­age. Since the beta few things have changed

• Email sender com­po­nent is now inte­grated with Core, so if you were using it, you now should look for it in Castle.Core.dll. The ver­sion shipped with Core 1.2 has the fol­low­ing major break­ing changes:
  — Removed Mes­sage, Mes­sageAt­tach­ment and Mes­sageAt­tach­ment­Col­lec­tion classes and replaced them with MailMes­sage, Attach­ment and Attach­ment­Col­lec­tion from .NET classes in System.Net.Mail
• Log­ging ser­vices (inte­gra­tion of Castle’s log­ging abstrac­tion with log4net and NLog) is now pack­aged with Core. Notice that these are depen­dent on Core (just like it used to be). Cas­tle does not have depen­dency on any of these, so don’t freak out.
• few minor bugs were fixed, but noth­ing seri­ous. You should be able to just switch the ref­er­ence to new ver­sion and start using it with no changes to your code.
• We ship four ver­sions: for .NET 2.0, for .NET 3.5, for Sil­verlight 3.0 and for Mono 2.6

Get it here.

Dynamic Proxy 2.2

This is a pretty sig­nif­i­cant release. If you haven’t before, read what we had in beta. Since then, the fol­low­ing has changed

• Inter­face mem­bers on prox­ies are behav­ing almost iden­ti­cal to ver­sion 2.1 (change from beta). That means that they take long name of explicit imple­men­ta­tion (InterfaceName.Method() instead of Method()), only if you already have a method called Method() on your proxy, either from base class or other inter­face. And even then, it will still be pub­lic, which makes it more trans­par­ent to the user.
• We ship three ver­sions: for .NET 2.0 (this is the last ver­sion to sup­port .NET 2.0), .NET 3.5 and Sil­verlight 3.0

Get it here.

MicroKernel/Windsor 2.1.1 (with sup­port for Silverlight)

Prob­a­bly the biggest thing about this release is that it includes a Sil­verlight ver­sion. There are a cou­ple more high­lights thought

• revamped typed fac­tory facil­ity
• added abil­ity to spec­ify Type For­ward­ing via XML con­fig with the fol­low­ing syntax:

  <component

    id="hasForwards"

    type="Castle.MicroKernel.Tests.ClassComponents.TwoInterfacesImpl, Castle.MicroKernel.Tests"

    service="Castle.MicroKernel.Tests.ClassComponents.ICommon, Castle.MicroKernel.Tests">

    <forwardedTypes>

      <add service="Castle.MicroKernel.Tests.ClassComponents.ICommon2, Castle.MicroKernel.Tests" />

    </forwardedTypes>

  </component>

• added Dynam­ic­Pa­ra­me­ters (with addi­tional option to return del­e­gate to be called upon component’s destruction)
• added OnCre­ate method, which lets you act upon com­po­nent after it’s cre­ated, and before it’s removed (see this Tehlike’s post. Notice it’s not in a facil­ity now, so it just works out of the box.)
• added lazy com­po­nent loader
• major per­for­mance improve­ments in cer­tain sce­nar­ios
• and many bug­fixes, see com­mit log for full list if you’re interested
• We ship two ver­sions: for .NET 3.5 and for Sil­verlight 3.0
• There is also log­ging facil­ity included in the pack­age. Again – nei­ther Micro­Ker­nel, nor Wind­sor depend on it, so don’t freak out.

Get it here.

We're already gath­er­ing ideas for the next ver­sion, so go ahead to the Cas­tle User­Voice page and tell us, what you'd like to see in the next version!

In Castle, DynamicProxy, Windsor. Both comments and pings are currently closed.