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.
Install-Package AppDomainToolkit -Version 22.214.171.124
dotnet add package AppDomainToolkit --version 126.96.36.199
<PackageReference Include="AppDomainToolkit" Version="188.8.131.52" />
paket add AppDomainToolkit --version 184.108.40.206
#r "nuget: AppDomainToolkit, 220.127.116.11"
// Install AppDomainToolkit as a Cake Addin #addin nuget:?package=AppDomainToolkit&version=18.104.22.168 // Install AppDomainToolkit as a Cake Tool #tool nuget:?package=AppDomainToolkit&version=22.214.171.124
This package has no dependencies.
NuGet packages (4)
Showing the top 4 NuGet packages that depend on AppDomainToolkit:
Creates dynamic persistent assemblies. The XAF user interface allows us to create an assembly without writing a single line of code. Advanced users can even use c# scripting and create new code generation templates. To debug in VS enable Source Server support under Tools/Options/Debugging. Blogs: http://apobekiaris.blogspot.com/search/label/WorldCreator
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