AppDomains don't work (aspnet50) #985
Comments
@bricelam can't repo this on |
Nothing special here. I'm using 1.0.0-rc1-10781 as well. Here is my entire source code. using System;
namespace Test
{
public static class Program
{
public static void Main()
{
AppDomain.Create("Test");
}
}
} ...and project.json {
"frameworks": {
"aspnet50": { }
}
} ...and
|
Yea it doesn't work. Set the http://msdn.microsoft.com/en-us/library/system.appdomainsetup.appdomainmanagerassembly(v=vs.110).aspx to null or empty string and see if that works. |
This works
|
@davidfowl So any existing libraries for net45 that don't do this will break? |
For now. I'm sure there's a way to make this work without having to null out the appdomain manager. We just need to set the right flags or something like that. |
I believe this works now without having to specify the domain manager as empty string |
Just tried it and I'm getting a new error: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at DomainManager.BindApplicationMain(ApplicationMainInfo& info)
at DomainManager.InitializeNewDomain(AppDomainSetup appDomainInfo)
at System.AppDomain.CreateAppDomainManager()
at System.AppDomain.Setup(Object arg)
at System.AppDomain.nCreateDomain(String friendlyName, AppDomainSetup setup, Evidence providedSecurityInfo, Evidence creatorsSecurityInfo, IntPtr p
arentSecurityDescriptor)
at System.AppDomainManager.CreateDomainHelper(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
at System.AppDomainManager.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
at System.AppDomain.InternalCreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
at System.AppDomain.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
at System.AppDomain.CreateDomain(String friendlyName)
at ConsoleApp1.Program.Main(String[] args) in C:\Users\davifowl\Documents\Visual Studio 14\Projects\WebApplication7\src\ConsoleApp1\Program.cs:line
10 We'll have to clean up our AppDomainManager so make it handle this. |
Fixed in 16fd19a |
The following code...
...throws the following exception.
The text was updated successfully, but these errors were encountered: