Castle.Services.Transaction
Castle.Service.Transaction was inspired by the Java Transaction API (JTA), although it is a simplified version with no support for two phase commit. Basically there is a transaction manager that is able to create transactions, that are associated with the thread. You can only have one active transaction per thread. The transaction object only orchestrates the resources enlisted with it. It is up to the resource implementation to provide integration with some external transaction-capable entity, typically a database connection.
Install
dotnet add package Castle.Services.Transaction --version 2.5.0
Install-Package Castle.Services.Transaction -Version 2.5.0
<PackageReference Include="Castle.Services.Transaction" Version="2.5.0" />
Frameworks
No framework metadata available.
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.