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.


This package has no dependencies.

Showing the top 3 GitHub repositories that depend on AppDomainToolkit:

Repository Stars
SharpLab (previously known as TryRoslyn)
Adds third-party support for RGB keyboards to games.
DevExpress XAF extension framework. To get notified on new releases posts, etc. follow us on twitter @expandframework or simply Star/watch this repository and get notified from GitHub and its verbose RSS feeds

Version History

Version Downloads Last updated 71,420 12/16/2014 540 12/16/2014 3,325 6/22/2013
1.0.4 678 6/22/2013
1.0.3 724 5/21/2013
1.0.2 756 11/26/2012 605 11/24/2012 595 11/24/2012
1.0.1 615 11/22/2012
1.0.0 1,487 11/22/2012