Badgerati/Edison

Test assemblies should be run in separate AppDomain with configs loaded

Badgerati opened this issue · 1 comments

Currently all of the test assemblies are loaded onto the current AppDomain, this is all right until a test wants to reference values within the AppSettings of that assembly's app.config. The issue is that the app.config for that AppDomain will actually be the console's or the GUI's.

Some references on how to do this can be found here: http://stackoverflow.com/questions/11993546/app-config-for-dynamically-loaded-assemblies and here: http://stackoverflow.com/questions/658498/how-to-load-an-assembly-to-appdomain-with-all-references-recursively

Managed to find a simpler way of injecting the app.config into the current AppDomain.