Change hardcoded usage of Microsoft.CSharp.CSharpProvider to instantiate it using CodeDomProvider.CreateProvider

[burningice2866]

Change hardcoded usage of Microsoft.CSharp.CSharpProvider to instantiate it using CodeDomProvider.CreateProvider

This gives the flexibility to configure dynamic compilation via app/web.config, ie. using Roslyn for newer C# features.

Implements feature #735

[VolodymyrMuzyka]

@napernik it will be included in next release? Now in order to upgrade, we have to comment reference to Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider

[burningice2866]

@napernik it will be included in next release? Now in order to upgrade, we have to comment reference to Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider

The change gives the flexibility for C1 to use the provider defined in web.config when compiling code, so it's optional to use Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider or keep using the Orchestra provider currently used by asp.net.

Basically this how it always should have been from the beginning, then it wouldn't have been an issue.

[burningice2866]

@aeont

• before: var csCompiler = new CSharpCodeProvider()
• now: var csCompiler = (CSharpCodeProvider)CodeDomProvider.CreateProvider("c#")

Whats the big deal, they are both of type CSharpCodeProvider ?? While before, it was 100% tied to the compiler builtin and shipped with .Net Full Framework, now we can make our own compiler which inherits from CSharpCodeProvider, register it in web.config and magically C1 will use that for its compiling.

[burningice2866]

Can we soon get this merged so its possible to test it "in the field" on builds based of the dev-branch?