Browse by term
How Castle Windsor resolves multiple implementations of the same interface and how registration order, named components, and constructor dependencies can build a Chain of Responsibility
Why Castle Windsor cannot be used with the .NET Framework 3.5 Client Profile.
Notes on ArcGIS Add-In limitations and packaging, including component namespaces, adding unreferenced assemblies as AddInContent, PDB handling, and extending the table context menu with buttons.
A short comparison of .NET IoC containers including StructureMap, LightCore, Autofac, Castle Microkernel, Castle Windsor, and Spring.NET, with a focus on XML configuration, keyed implementations, and assembly resolution.