Castle Core provides common Castle Project abstractions including logging services. It also features Castle DynamicProxy a lightweight runtime proxy generator, and Castle DictionaryAdapter.
See the documentation.
See the Releases.
Debugging symbols are available in symbol packages in the AppVeyor build artifacts since version 4.1.0. For example, here are the artifacts for 4.1.0.
Castle Core is © 2004-2019 Castle Project. It is free software, and may be redistributed under the terms of the Apache 2.0 license.
Browse the contributing section of our Home repository to get involved.
| Platforms | Build Status | NuGet Feed |
|---|---|---|
| Windows & Linux | Preview Feed |
build.cmd
Compilation requires an up-to-date .NET Core SDK and MSBuild 15+ (which should be included in the former).
Running the unit tests additionally requires the .NET Framework 4.6.1+ as well as the .NET Core 3.1 runtime to be installed.
Most of these requirements should be covered by Visual Studio 2019.
./build.sh
Compilation requires an up-to-date .NET Core SDK.
Running the unit tests additionally requires the .NET Core 3.1 runtime to be installed, as well as either Docker or Mono. For the latter, we recommend Mono 5.10+, though older versions (4.6.1+) might still work as well.
ℹ️ Mono runtime support: Castle Core runs with minor limitations and defects on Mono 4.0.2+ (however 4.6.1+ is highly recommended, or 5.10+ if your code uses new C# 7.x language features such as in parameters).
We test against up-to-date Mono versions in order to fix known defects as soon as possible. Because of this, if you are using an older Mono version than our Continuous Integration (CI) build, you might see some unit tests fail.
For known Mono defects, check our issue tracker, as well as unit tests marked with [ExcludeOnFramework(Framework.Mono, ...)] in the source code.
The following conditional compilation symbols (vertical) are currently defined for each of the build configurations (horizontal):
| Symbol | .NET 4.5 | .NET Standard 2.x |
|---|---|---|
FEATURE_APPDOMAIN |
✅ | 🚫 |
FEATURE_ASSEMBLYBUILDER_SAVE |
✅ | 🚫 |
FEATURE_EVENTLOG |
✅ | 🚫 |
FEATURE_REMOTING |
✅ | 🚫 |
FEATURE_SERIALIZATION |
✅ | 🚫 |
FEATURE_SYSTEM_CONFIGURATION |
✅ | 🚫 |
FEATURE_TEST_COM |
✅ | 🚫 |
FEATURE_TEST_PEVERIFY |
✅ | 🚫 |
FEATURE_TEST_WINFORMS |
✅ | 🚫 |
| --- | ||
DOTNET45 |
✅ | 🚫 |
FEATURE_APPDOMAIN- enables support for features that make use of an AppDomain in the host.FEATURE_ASSEMBLYBUILDER_SAVE- enabled support for saving the dynamically generated proxy assembly.FEATURE_EVENTLOG- provides a diagnostics logger using the Windows Event Log.FEATURE_REMOTING- supports remoting on various types including inheriting from MarshalByRefObject.FEATURE_SERIALIZATION- enables support for serialization of dynamic proxies and other types.FEATURE_SYSTEM_CONFIGURATION- enables features that use System.Configuration and the ConfigurationManager.FEATURE_TEST_COM- enables COM Interop tests.FEATURE_TEST_PEVERIFY- enables verification of dynamic assemblies using PEVerify during tests. (Only defined on Windows builds since Windows is currently the only platform where PEVerify is available.)FEATURE_TEST_WINFORMS- enables Windows Forms tests.