-
-
Notifications
You must be signed in to change notification settings - Fork 731
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 .NET Core 3 to Cake.Tool update to .NET Core 3 SDK #2603
Comments
* Updated SDK to .NET Core 3 (3.0.100-preview8-013656) * Added netcoreapp3.0 moniker to Cake.Tool * Added netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidated Cake.Tool.csproj into Cake.csproj (sorts VS2019 issues) * fixes cake-build#2603
* Updated SDK to .NET Core 3 (3.0.100-preview9-014004) * Added netcoreapp3.0 moniker to Cake.Tool * Added netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidated Cake.Tool.csproj into Cake.csproj (sorts VS2019 issues) * fixes cake-build#2603
* Updated SDK to .NET Core 3 (3.0.100-preview9-014004) * Added netcoreapp3.0 moniker to Cake.Tool * Added netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidated Cake.Tool.csproj into Cake.csproj (sorts VS2019 issues) * fixes cake-build#2603
* Updated SDK to .NET Core 3 (3.0.100-preview9-014004) * Added netcoreapp3.0 moniker to Cake.Tool * Added netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidated Cake.Tool.csproj into Cake.csproj (sorts VS2019 issues) * fixes cake-build#2603
* Update SDK to .NET Core 3 (3.0.100-rc1-014190) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1-beta3-final (needs to be non-prerelease before merge) * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 * Temp fix for rollforward test * fixes cake-build#2603
* Update SDK to .NET Core 3 (3.0.100-rc1-014190) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1-beta3-final (needs to be non-prerelease before merge) * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 * Temp fix for rollforward test * fixes cake-build#2603
Please update nuget package to .NET Core 3.0, Thanks! |
* Update SDK to .NET Core 3 (3.0.100) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1 * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 * Temp fix for rollforward test * fixes cake-build#2603
Meanwhile you can use the .NET Core 2.1 tool in a pure 3.0 SDK environment by setting the environment key |
* Update SDK to .NET Core 3 (3.0.100) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1 * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 * Temp fix for rollforward test * fixes cake-build#2603
* Update SDK to .NET Core 3 (3.0.100) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1 * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 * Temp fix for rollforward test * fixes cake-build#2603
I'm having trouble running dotnet cake CLI commands on Azure Pipelines. I'm manually installing. NET Core 3.0 but getting this error when I run 'dotnet cake':
What I don't understand is that AppVeyor still works. Do I need to wait for this upgrade to be released or is something else going on? Links to my repo and Build output. |
@RehanSaeed have you set environment variable |
No. Azure Pipelines already has older versions of. NET Core installed on their hosted build machines, so in theory I shouldn't need to right? I guess it wouldn't hurt to try. |
Could be that the steps:
- task: UseDotNet@2
displayName: 'Use .Net Core sdk 2.1.202'
inputs:
version: 2.1.202
- task: UseDotNet@2
displayName: 'Use .Net Core sdk 2.1.701'
inputs:
version: 2.1.701
- task: UseDotNet@2
displayName: 'Use .Net Core sdk 3.0.100'
inputs:
version: 3.0.100 Setting |
According to the docs:
It says previous versions should still work. |
* Update SDK to .NET Core 3 (3.0.100) * Add netcoreapp3.0 moniker to Cake.Tool * Add netcoreapp3.0 moniker to Unit tests * Execute unit tests under netcoreapp3.0 * Consolidate Cake.Tool.csproj into Cake.csproj (sorts VS2019 rebuild issues) * Refactor Runtime Framework detection * Microsoft.CodeAnalysis.CSharp.Scripting 3.3.1 * Remove mono workaround * Add .NET Core rollForward policy * Build script cleanup * Update NuGet command line to 5.2.0 (5.3.0 not blessed yet) * Update NuGet Client libs to 5.3.0 * Temp fix for rollforward test * fixes cake-build#2603
Adding |
GH2603: Added .NET Core 3 moniker to Cake.Tool
@patriksvensson What is the ETA for a release of Cake.Tool? Does it get release separetely from the rest of cake? |
@RehanSaeed it gets released at the same time as Cake, not separately. It is on the Azure Artifacts feed though: |
The text was updated successfully, but these errors were encountered: