In the 3.6 update, we botched the handling of the "aspnet:RoslynCompilerLocation" appSetting. Prior to that version, we
would add that value to app.config files, but not web.config. With the update, we started treating all config files the same,
not adding that setting anymore.
Web apps have a 'bin' directory where all their assemblies get deployed. We also deploy roslyn to this bin directory.
Non-web apps don't have 'bin', but instead just a base AppDomain directory. This is where we deploy roslyn in non-web scenarios.
Instead of requiring a silly 'aspnet:*' appSetting for non-aspnet apps to use this package, let's just check the appdomain base
directory as a default location.
In the 3.6 update, we botched the handling of the "aspnet:RoslynCompilerLocation" appSetting. Prior to that version, we would add that value to app.config files, but not web.config. With the update, we started treating all config files the same, not adding that setting anymore.
Web apps have a 'bin' directory where all their assemblies get deployed. We also deploy roslyn to this bin directory. Non-web apps don't have 'bin', but instead just a base AppDomain directory. This is where we deploy roslyn in non-web scenarios.
Instead of requiring a silly 'aspnet:*' appSetting for non-aspnet apps to use this package, let's just check the appdomain base directory as a default location.