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
dotnet add package AppDomainToolkit --version
<PackageReference Include="AppDomainToolkit" Version="" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add AppDomainToolkit --version
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: AppDomainToolkit,"
For F# scripts that support #r syntax, copy this into the source code to reference the package.


This package has no dependencies.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on AppDomainToolkit:

Package Downloads
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:
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:

Repository Stars
.NET language playground

Version History

Version Downloads Last updated 134,428 12/16/2014 793 12/16/2014 4,124 6/22/2013
1.0.4 960 6/22/2013
1.0.3 1,003 5/21/2013
1.0.2 1,024 11/26/2012 872 11/24/2012 863 11/24/2012
1.0.1 887 11/22/2012
1.0.0 3,530 11/22/2012