Conversation
Running the text templating engine within Visual Studio for Mac fails since the RuntimeInfo fails to find any SDK directory. When using the Roslyn code compiler there is now no exception if no SDK is found. The SDK location is not needed for the Roslyn compiler since there is no external csc.dll to run. Also use a better default C# lang version for the Roslyn code compiler instead of 7.0
The CSharpParseOptions was not using the best language version. The CSharpParseOptions was created but no language version was used from the RuntimeInfo nor the language version specified by the Roslyn code compiler.
Not needed on the RuntimeInfo class anymore.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not sure if this the best approach. I tried to minimise the changes needed to get t4 templating working in VS Mac 17.x