You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the current version of System.CodeDom throws PlatformNotSupported for every CompileAssembly* method of CSharpCodeGenerator since they all end up to the method FromFileBatch which throws that exception systematically. Just wondering whether this is still the current state of development or should it already work. Everything works well in my experiment project if I just change the target framework from netcoreapp2.0 to net462.
That's unfortunately by-design as the compilers are not part of the .NET Core runtime. However, given that CodeDOM isn't referenced by the core (it only comes in when people depend on it/via the compat pack) we could probably fix this.
@weshaggard, any reason why the CodeDOM NuGet package couldn't depend on Roslyn? Practically speaking, folks depending on CodeDOM probably need to compile anyways so probably end up pulling in Roslyn anyway. The benefit of us doing it avoids consuming code having to pipe the data & settings correctly through to Roslyn.
The text was updated successfully, but these errors were encountered:
Reported by @jlahteen:
That's unfortunately by-design as the compilers are not part of the .NET Core runtime. However, given that CodeDOM isn't referenced by the core (it only comes in when people depend on it/via the compat pack) we could probably fix this.
@weshaggard, any reason why the CodeDOM NuGet package couldn't depend on Roslyn? Practically speaking, folks depending on CodeDOM probably need to compile anyways so probably end up pulling in Roslyn anyway. The benefit of us doing it avoids consuming code having to pipe the data & settings correctly through to Roslyn.
The text was updated successfully, but these errors were encountered: