How to keep ASP.NET assemblies in AppDomain alive?
Scenario: I’ve an n-Tier enterprise ASP.NET application deployed using Web Deployment Projects. All tiers produce independent assemblies that is consumed by the ASP.NET application.
appdomain
ASP.NET restarts when a folder is created, renamed or deleted
UPDATE — process to replicate issue:
ASP.NET Data Cache – preserve contents after app domain restart
I am using ASP.NET’s data caching API. For example:
How can I switch .NET assembly for execution of one method?
I have different versions of dlls for my .NET application and most of the time I want to use the latest one. However, there is one method which I run on a separate thread where I need to be able to select an older version of the dll based on some criteria.
SynchronizationContext.Current is null when run on different app domains
I have a Web Application running in one machine and the services in another machine (i.e.both are in different App domains). I have a workflow service in my service layer which gets the Synschronization Context from SynchronizationContext.Current. I get the SynchronizationContext.Current always as null. But If I run both my application and service layer in the same machine (i.e. same appdomain) the SynchronizationContext.Current is AspNetSynchronizationContext and it works fine. Can somebody help me to resolve this to run different app domains.
Create application domain and load assembly
I want to create an application domain with default permissions and load assembly into the application domain with default privileges and execute the methods inside the assembly.