Open sander1095 opened 2 months ago
I've also posted a question on StackOverflow to get some more assistance: https://stackoverflow.com/questions/78667998/why-is-azure-pipelines-installing-the-wrong-net-sdk-version-according-to-globa
The SO post has been answered. Apparently ,the .NET install task just installs the version specified and doesn't care about the rollForward
. I feel like this could be improved, though
New issue checklist
Task name
UseDotNet
Task version
2
Issue Description
I'm using the following task:
with the following
global.json
latestFeature
should install the latest feature band version, meaning8.0.xxx
. At the time of writing, this is8.0.302
.However, it installs
8.0.301
, which is not desired. I am usinglatestFeature
to ensure I always get the latest feature bands and security patches.Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows-Latest
Relevant log output
Full task logs with system.debug enabled
Repro steps