-
Notifications
You must be signed in to change notification settings - Fork 166
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
.NET Core 3 support #473
Comments
We are currently working with .Net Core 3 support. You can follow this branch for the progress on this. https://github.com/filipw/dotnet-script/tree/feature/netcoreapp3.0 |
Is there any way to run a preview version of the .Net Core 3 version? |
Looking forward to this! I have built an EF 6.3 code generator for .NET Core using CSX files, but the assembly loading mechanism in 3.0 is causing some problems. You can see it demonstrated here: https://github.com/robertmclaws/EDMXParsingSample. I'm actually glad it happened because it exposed a flaw in the EF6.3 metadata parsing code, but it's slowed my plans for releasing my framework. I'm generating the code with a Thanks for all your efforts on this project! |
The branch you're mentioning in your link is gone. What is the progress so far? |
That is because we have merged it to master. We are working on the final bits now |
We have just released version 0.50.0 adding support for .Net Core 3.0 |
@seesharper , are there any upgrade instructions? From what I can tell, the two places that need updates are in the omnisharp.json and launch.json file
|
|
Can you please add .net core 3 support for the global tool? Background: I use scripting in a CI/CD pipeline. Since I upgraded to the .net core 3 docker image from microsoft, i can't install the dotnet script tool anymore. I think its just a small change in the TargetFrameworks msbuild property to support both, .net core 2.1 and .net core 3.
The text was updated successfully, but these errors were encountered: