-
Notifications
You must be signed in to change notification settings - Fork 105
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
Add option to use compiler from Visual Studio #86
Comments
Have you fixed this? It's this: https://github.com/SubSonic-Core/SubSonic.Core.TextTemplating/tree/master/Mono.TextTemplating.Roslyn |
not completely fixed. if your using .net framework < 5 I am pretty sure it is still using the rosyln engine installed there which for my system is still C# 5. however, I have the .net to .net core bridge working via RPC and the T4 Host for .net core is using the roslyn engine installed with .net core 3.1 and that is C# 8.0 |
when you look here: https://github.com/dotnet/roslyn/blob/master/docs/wiki/NuGet-packages.md As you use 3.6 it should contain at least c#8 |
i think if you switch to 3.8, you could use c#9 features |
could you enable issues in your branch?
returns false, but why is it needed? |
path rooted location is defined as the c:\***.dll location on a physical drive and anything else is is essential not resolved. this is an example of a t4 template that I use to generate DAL wrapper.
this is also an implementation of a transformation host that you will not find in the mono text templating. but it is derived from a subclass which is found in the code you are linking. The transformation host can use nuget package references to resolve assembly's this is just one piece required and is out of a visual studio 2019 extension that make the mono engine useable inside visual studio and overrides/replaces the stock implementation of the t4 templating service which is out of box with VS 2019. there is quite a lot to deal with when making sure the assemblies are path rooted for the roselyn engine.
|
By design it uses the compiler that comes with the framework that's hosting it. If you use the global tool version, which is currently the primary use case, then it will use the compiler shipped with .NET Core. If you're hosting the library yourself, then you can choose to also reference the By design it does not search for the compiler shipped with Visual Studio, as this would mean that apps that use the library would depend on Visual Studio, which is not a good default behavior as it could cause apps to run correctly on developer machines and fail on other machines. However, I would be open patches that add a method to pass in a custom compiler path or to enable use of the Visual Studio compiler e.g. |
How can I go about ensuring that Mono.TextTemplating is using the Roslyn compiler that comes with the currently installed version of visual studio?
The text was updated successfully, but these errors were encountered: