Krzysztof Koźmic's blog

As promised, I released Nuget pack­ages for beta 1 of Wind­sor 3. This is my first major roll­out of Nuget pack­ages, so please report any issues work­ing with them.

Nuget and beta packages

Nuget is quickly evolv­ing and get­ting more use­ful with each release. How­ever one fea­ture it’s miss­ing right now is sup­port for pre-release pack­ages (this is com­ing in the next ver­sion).

This is not really a big deal, how­ever it means there are a few things you should be aware of.

Rec­om­mended version

Since the new pack­age is a pre-release, while I would really like for every­one to start using it imme­di­ately and report all issues they find, I quite under­stand that many peo­ple will rather pre­fer to stick to the last offi­cial ver­sion for the time being. To accom­mo­date that the new pack­ages are not made rec­om­mended ver­sions, so your Nuget explorer will still point to the last sta­ble (2.5.3) ver­sion if you search for Wind­sor, Castle.Core or any other pre-existing package.

If you go to com­mand line and install one of the pack­ages with­out spec­i­fy­ing ver­sion num­ber, it will install the lat­est, that is beta 1 version.

SymbolSource.org and debug­ging into Windsor

Folks at SymbolSource.org added recently sup­port for Nuget (and Open­Wrap as well) and the new Cas­tle pack­ages take advan­tage of that. What it gives you, is you can now eas­ily debug into Windsor’s code, just like .NET frame­work ref­er­ence source (there’s a sim­ple guide at Sym­bol­Source on how to do it).

After you’re all set you can step into any of Cas­tle meth­ods in your debug­ger and watch the magic hap­pen. Very cool thing, even if I say so myself.

List of packages

Here’s the full list of v3 beta 1 pack­ages (notice those are not all Cas­tle pack­ages, just those that were pub­lished as v3 beta 1 roll­out of Windsor):

• Castle.Core – Con­tains Castle.Core.dll which includes Dynam­icProxy, Dic­tio­naryAdapter, EmailSender, log­ging abstrac­tions and some other goodies.
• Castle.Core-log4net – Con­tains Castle.Services.Logging.Log4netIntegration.dll, that is imple­men­ta­tion of Cas­tle log­ging abstrac­tions for log4net
• Castle.Core-NLog – Con­tains Castle.Services.Logging.NLogIntegration.dll, that is imple­men­ta­tion of Cas­tle log­ging abstrac­tions for NLog
• Castle.Windsor – Con­tains Castle.Windsor.dll which has Wind­sor itself and two most com­monly used facil­i­ties – Typed Fac­tory facil­ity and Startable facil­ity.
• Castle.LoggingFacility – Con­tains log­ging facil­ity.
• Castle.Windsor-log4net – Empty pack­age that just installs log­ging facil­ity and Castle.Core-log4net (and their depen­den­cies obviously).
• Castle.Windsor-NLog – Empty pack­age that just installs log­ging facil­ity and Castle.CoreNLog (and their depen­den­cies obviously).
• Castle.WcfIntegrationFacility – Windsor’s WCF facil­ity.
• Castle.SynchronizeFacility – Windsor’s Syn­chro­nize facil­ity.
• Castle.RemotingFacility – Windsor’s Remot­ing facil­ity (extracted out of Castle.Windsor.dll)
• Castle.EventWiringFacility – Windsor’s Event Wiring facil­ity (extracted out of Castle.Windsor.dll)
• Castle.FactorySupportFacility– Windsor’s Fac­tory Sup­port facil­ity (extracted out of Castle.Windsor.dll)

I hope this will make it eas­ier for every­one to test drive Wind­sor. And if you find any issues, have any sug­ges­tions or ideas, do not hes­i­tate to bring them up, either on our google group, or issue tracker.