I want to enumerate all loaded assemblies in an Asp.NET application, using AppDomain.CurrentDomain.GetAssemblies(). However, when checking the documentation for AppDomain, I find the following stateme
What is exactly is an Application Domain (AppDomain)开发者_运维技巧 and how is it different than a process or thread?See MSDN.
From What is a开发者_StackOverflow .NET Application Domain?: You can run several application domains in a single process with the same level of isolation that would exist in separate processes, but
I am having trouble figuring something out about my AppDomain.Unload(...) call. I have a detailed explanation with code from my earlier question. As it turns out, I was performing a couple of steps th
I am thinking about a system that is based on plugins. I am going to create my plugins in each AppDomain and talk with them via Name Pipes in WCF. But I also want each of my plugins have some sort of
If I instance a new Process in which I then create a new AppDomain, I\'m wondering what is the safest way to end the Process. Should I:
UPDATE -- process to replicate issue: 1) Create a website project at c:\\projects\\restart-demo 2) Add default web.config and a dummy aspx page test.aspx
I have a marker interface something like this: [AttributeUsage(AttributeTargets.Method, AllowMultiple=false, Inherited=true)]
This question already has answers here: Closed 12 years ago. Possible Duplicate: How to prevent an ASP.NET application restarting when the web.config is modified?
I need to execute a method in an assembly loaded during runtime. Now I want to unload those loaded assemblies after the method call. I know that I need a new AppDomain so I can unload the libraries. B