appdomain

Having a WebApi 2.2 application - is it possible to make use of AppDomain's UnhandledException hook? I have a code similar to this: [assembly: OwinStartup("DevConfiguration", typeof(DevStartup))] namespace WebApi.Module { public class DevStartup { private const string ErrorEventSourceName = "WebApiHost"; private const int ErrorEventId = 600; [SecurityPermission(SecurityAction.Demand, Flags=SecurityPermissionFlag.ControlAppDomain)] public void Configuration(IAppBuilder app) { AppDomain.CurrentDomain.UnhandledException += AppDomain_UnhandledException; ... throw new Exception("some exception); }

.NET 4.5, 64bit Win8 I have two MSMQ running under WCF and hosted under Windows Activation Service. Execute MSMQ: Responsible for calling an unmanaged function and obtaining a pointer IntPtr to 4GB array in addition to other limited size variables. This array is not that important and shouldn't be blocking the queue until it is passed to the DB and having this queue free is a priority. Passing the pointer to the Save MSMQ (Hypothesis). Save MSMQ: Should save the array to the DB across the network then deallocate it from unmanaged memory. The problem here would be: Making sure the array is

Somehow I assumed that delegates passed to another AppDomain would turn into a proxy as if it were an object derived from MarshalByRefObject . Unfortunately, it seems they don’t. Let’s say in my code I have a class MyClass like this: [Serializable] public sealed class MyClass { public Func<Input, Output> SomeDelegate; } [Serializable] public sealed class Input { ... } [Serializable] public sealed class Output { ... } Now I need to pass an instance of MyClass to another AppDomain. The problem is that the delegate stored in SomeDelegate may contain a reference to pretty much any method,

I have relatively simple application, but warm (second, etc.) start-up time is awful 3-5 seconds. Profiler (VS2010, CPU Sampling) shows that more than 80% of time is spent in Application.RunInternal (~40%) and XamlRader.LoadBaml (~40%) functions. The root of the problem is that Window is created in non-default AppDomain. If I move Window creation to default AppDomain or give AppDomain unrestricted permission set everything is as fast as expected. I'm testing on: Windows Seven x64 .Net 4.0 4Gb RAM GeForce 9800GT 1Gb. I'm creating AppDomain this way var permissionSet = new PermissionSet(null);

Here's some sample code: using System; namespace UnloadFromFinalizer { class Program { static void Main(string[] args) { Program p = new Program(); } AppDomain domain; Program() { this.domain = AppDomain.CreateDomain("MyDomain"); } ~Program() { AppDomain.Unload(this.domain);//<-- Exception thrown here } } } I have a class that creates an AppDomain in the constructor to be used over the lifetime of the object. I'd like to properly cleanup the AppDomain, so I thought I would call Unload in the finalizer. Unfortunately, that causes a CannotUnloadAppDomainException to be thrown. The MSDN