dotnet add package AppDomainToolkit --version 184.108.40.206
NuGet\Install-Package AppDomainToolkit -Version 220.127.116.11
<PackageReference Include="AppDomainToolkit" Version="18.104.22.168" />
paket add AppDomainToolkit --version 22.214.171.124
#r "nuget: AppDomainToolkit, 126.96.36.199"
// Install AppDomainToolkit as a Cake Addin #addin nuget:?package=AppDomainToolkit&version=188.8.131.52 // Install AppDomainToolkit as a Cake Tool #tool nuget:?package=AppDomainToolkit&version=184.108.40.206
Anyone whose ever had to deal with loading Assemblies using standard .NET reflection facilities understands that it's not straightforward. Which context should I load into? How do I know that my Assembly is imported into the correct application domain? What if I want to load two versions of the same assembly into an application domain? How can I tear down an application domain where I've loaded my own assemblies? This package exists to provide a basic API for handling common AppDomain issues.
|Product||Versions Compatible and additional computed target framework versions.|
|.NET Framework||net is compatible.|
This package has no dependencies.
NuGet packages (3)
Showing the top 3 NuGet packages that depend on AppDomainToolkit:
Cireson Web UI
Cireson Platform SDK.
Provides NuGet based implementation for MetaPack solution packaging and deployment.
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on AppDomainToolkit:
.NET language playground