Updating Agent to latest .net8 patch and making changes to keep .net updated. #5399
+50
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Upgrade dev.sh with sophisticated .NET version management system - Add support for channel-based and version-specific .NET installations - Implement automatic newer version detection and warnings - Update to .NET 8.0.416 SDK and 8.0.22 Runtime (latest stable) - Replace deprecated mapfile with bash 3.2 compatible implementation - Add comprehensive version resolution for runtime installations - Improve Azure DevOps pipeline compatibility - Maintain existing ADO_ENABLE_LOGISSUE integration patterns - Ensure stderr warnings don't disrupt pipeline execution - Follow established ##vso[task.logissue] formatting standards Key improvements: - Enhanced version management with proactive update notifications - Better macOS compatibility (bash 3.2 support) - Maintained backward compatibility with existing build processes - Future-ready channel-based .NET installation support
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
- Replace GitHub API with official .NET feeds (builds.dotnet.microsoft.com) - Add fallback to ci.dot.net/public for reliability - Use proper version file parsing (tail -n 1) matching dotnet-install.sh - Fix version reporting accuracy (now shows correct current versions) - Improve error handling with graceful fallbacks This ensures version warnings are based on authoritative .NET release data rather than unreliable GitHub repository tags.
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
raujaiswal
approved these changes
Nov 19, 2025
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
rishabhmalikMS
approved these changes
Nov 21, 2025
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR
dev.shto raise warning if newer patch is avaiable.Description
see above
Risk Assessment (Low)
Low Risk - This change enhances existing functionality without breaking backward compatibility:
dev.shcommand signatures remain unchangedUnit Tests Added or Updated (No)
No unit tests required - this is a build script enhancement that follows existing patterns. The changes are primarily infrastructure improvements to the build system itself.
Additional Testing Performed
dev.shfunctionality remains intactChange Behind Feature Flag (No)
Feature flag is not applicable for build system infrastructure changes. This enhancement is internal to the development workflow and doesn't affect runtime agent behavior.
Tech Design / Approach
NA
Documentation Changes Required (No)
No external documentation changes needed. The
dev.shusage remains the same:Logging Added/Updated (Yes)
NA
Telemetry Added/Updated (No)
NA
Rollback Scenario and Process (Yes)
NA
Dependency Impact Assessed and Regression Tested (Yes)
NA
Files Changed: 1 file, +141 insertions, -13 deletions
Impact Scope: Build system enhancement only, no runtime agent changes