AppDomainToolkit 1.0.4.3
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 1.0.4.3
dotnet add package AppDomainToolkit --version 1.0.4.3
<PackageReference Include="AppDomainToolkit" Version="1.0.4.3" />
paket add AppDomainToolkit --version 1.0.4.3
Dependencies
This package has no dependencies.
Used By
NuGet packages (4)
Showing the top 4 NuGet packages that depend on AppDomainToolkit:
| Package | Downloads |
|---|---|
|
eXpandWorldCreator
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.Platform.Extension.WebUi
Cireson Web UI
|
|
|
Cireson.Platform.SDK
Cireson Platform SDK.
|
|
|
MetaPack.NuGet
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 |
|---|---|
|
ashmind/SharpLab
.NET language playground
|
