Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!

Update: Due to a regression error discovered in Windsor Factory Support Facility, we decided to act fast and provide updated package of Windsor, without the issue. Get it here. Sorry for the inconvenience.

Castle Project 

What better way of starting a new year can there be, than fresh set of releases from Castle Project?!

Core 1.2 (with more)

Castle Core 1.2 has now its own, separate package. Since the beta few things have changed

  • Email sender component is now integrated with Core, so if you were using it, you now should look for it in Castle.Core.dll. The version shipped with Core 1.2 has the following major breaking changes:
    - Removed Message, MessageAttachment and MessageAttachmentCollection classes and replaced them with MailMessage, Attachment and AttachmentCollection from .NET classes in System.Net.Mail
  • Logging services (integration of Castle’s logging abstraction with log4net and NLog) is now packaged with Core. Notice that these are dependent on Core (just like it used to be). Castle does not have dependency on any of these, so don’t freak out.
  • few minor bugs were fixed, but nothing serious. You should be able to just switch the reference to new version and start using it with no changes to your code.
  • We ship four versions: for .NET 2.0, for .NET 3.5, for Silverlight 3.0 and for Mono 2.6

Get it here.

Dynamic Proxy 2.2

This is a pretty significant release. If you haven’t before, read what we had in beta. Since then, the following has changed

  • Interface members on proxies are behaving almost identical to version 2.1 (change from beta). That means that they take long name of explicit implementation (InterfaceName.Method() instead of Method()), only if you already have a method called Method() on your proxy, either from base class or other interface. And even then, it will still be public, which makes it more transparent to the user.
  • We ship three versions: for .NET 2.0 (this is the last version to support .NET 2.0), .NET 3.5 and Silverlight 3.0

Get it here.

MicroKernel/Windsor 2.1.1 (with support for Silverlight)

Probably the biggest thing about this release is that it includes a Silverlight version. There are a couple more highlights thought

  • revamped typed factory facility
  • added ability to specify Type Forwarding via XML config with the following 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 DynamicParameters (with additional option to return delegate to be called upon component’s destruction)
  • added OnCreate method, which lets you act upon component after it’s created, and before it’s removed (see this Tehlike’s post. Notice it’s not in a facility now, so it just works out of the box.)
  • added lazy component loader
  • major performance improvements in certain scenarios
  • and many bugfixes, see commit log for full list if you’re interested
  • We ship two versions: for .NET 3.5 and for Silverlight 3.0
  • There is also logging facility included in the package. Again – neither MicroKernel, nor Windsor depend on it, so don’t freak out.

Get it here.

We're already gathering ideas for the next version, so go ahead to the Castle UserVoice page and tell us, what you'd like to see in the next version!


Posted 01-12-2010 6:06 PM by Krzysztof Koźmic
Filed under:

[Advertisement]

Comments

Eric Hauser wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-12-2010 12:51 PM

Is the documentation page going to be updated to reflect the version?  It still says Release Candidate 3 or Trunk which is pretty confusing for new users.

Krzysztof Koźmic wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-12-2010 1:14 PM

@Eric Hauser

Yes, we're moving to a wiki-based documentation engine and along with that, we'll update the docs.

Rob Eisenberg wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-12-2010 2:46 PM

I've had my eye on the calendar waiting for this release for some time :)  Congratulations!!!  As you may guess, the Silverlight support is the key for me.  I'm a very happy developer today :)

Krzysztof Koźmic wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-12-2010 3:35 PM

@Eric

Thanks for bringing this to my attention.

I updated the docs accordingly, for the time being until me move to new docs engine.

Dave wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-13-2010 8:01 AM

Awesome news! many thanks to you and the team for all their hard work!

Tim Barcz wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-17-2010 10:14 PM

Rock on this is awesome...great work Krzysztof

Paul Wideman wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-20-2010 2:44 PM

Just curious - why are the Castle binaries compiled without the AllowPartiallyTrustedCallers attribute by default? It's easy to recompile to add this attribute, but it would save me (and others I'm sure) some headache if the released binaries already had it set.

Krzysztof Koźmic wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 01-22-2010 3:36 AM

@Paul Wideman,

there was a discussion about that long time ago: groups.google.com/.../f6bd971e33a54a9c

Sanjeev Agarwal wrote Daily tech links for .net and related technologies - Feb 1-3, 2010
on 02-01-2010 6:02 AM

Daily tech links for .net and related technologies - Feb 1-3, 2010 Web Development Ambiguous Controller

Nicky wrote re: Castle Windsor 2.1, Dynamic Proxy 2.2 and more released!
on 06-20-2010 7:05 PM

Hi, I'm not sure if you are still monitoring this blog entry, but I hope you are.

Does your team have a solution for implementing your Castle.Windsor, Castle.MicroKernel and Castle.Core in a MEDIUM TRUST environment?  I have been trying everything to fix the security error I am getting, and nothing seems to work.

Here is the error:

System.Security.SecurityException: That assembly does not allow partially trusted callers

I'm pretty certain it's happening in the Castle.Windsor assembly

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Subscribe
Google Reader or Homepage

del.icio.us CodeBetter.com Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl CodeBetter.com Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of Devlicio.us
Red-Gate Tools For SQL and .NET

NDepend

SlickEdit
 
SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
LiteAccounting.Com
DevExpress
Fixx
NHibernate Profiler
Unfuddle
Balsamiq Mockups
Scrumy
JetBrains - ReSharper
Umbraco
NServiceBus
RavenDb
Web Sequence Diagrams
Ducksboard<-- NEW Friend!

 



Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers

 

Community Server (Commercial Edition)