-
Notifications
You must be signed in to change notification settings - Fork 0
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 5 compatibility #5
Comments
Just a quick look, it's probably not .NET 5 causing the issue but the absence of .NET Core 2.0 (EOL now). Since you only have .NET 5 installed (not even 3.1), this tool would need to target .NET 5 specifically. I should probably upgrade this to 3.1 (LTS) and you could install that as well. Let's see if I can target both 3.1 and 5.0. Time to finally take some time and improve this tool, it seems. :-) |
Looks like dotnet CLI tools only support .NET Core 2.2 or lower. It's nothing I can change now. Please refer to the linked issue. The latest version of this tool might thus be impossible to use. Workaround: Use the previous version 0.3.2 of DotnetSshDeploy and install the .NET Core 2.1 runtime. |
Should be fixed now. Please use the latest release 0.4.1 and follow the new instructions for .NET tools in the README file. Note that the .NET 5.0 runtime is now required. Older .NET Core runtimes are no longer compatible with this latest release. Version 0.3.2 is functionally identical for now but newer development will be based on .NET 5.0. |
I recently created a .NET 5 project and enabled CI/CD on gitlab to deploy the website (MVC) automatically after build.
This failed due to an un-met dependency (Microsoft.NETCore.App v2.0.0).
I think, this might not only happen for .NET 5 projects but for other CD builds too (not tested yet).
The variables are correct and contain the right content (double checked before writing the issue).
See the build log:
The text was updated successfully, but these errors were encountered: