-
Notifications
You must be signed in to change notification settings - Fork 43
made ICompilerSettings and CSharpCodeProvider ctor public #55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…CodeProvider also public
@trullock The original goal for this package is to enable asp.net to leverage Roslyn compilers for dynamical compilation. In that context, it doesn't make sense to expose the non-default-constructor, since asp.net only uses default constructor. |
@@ -4,7 +4,7 @@ | |||
using System; | |||
|
|||
namespace Microsoft.CodeDom.Providers.DotNetCompilerPlatform { | |||
internal interface ICompilerSettings { | |||
public interface ICompilerSettings { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add some comments?
@@ -18,8 +18,12 @@ public CSharpCodeProvider() | |||
: this(null) { | |||
} | |||
|
|||
// Constructor used for unit test purpose | |||
internal CSharpCodeProvider(ICompilerSettings compilerSettings = null) { | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please also update VBCodeProvider?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. :)
Excellent. Can we get a 2.0.1 nuget of this soon? |
Its unclear why CompilationSettings doesn't allow falling back to the tooling installed on the dev environment, or to use a csc compiler from a different location that whats shipped with this assembly.
By making the ICompilerSettings interface public this becomes trivial.
I don't see any reason for this to be internal