Migrate to HTTP client

[josesimoes]

Description

• Migrate to HTTP client.

Motivation and Context

• Replacing obsolete API.

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

Summary by CodeRabbit

• Chores
  • Refined the system’s dependency framework by introducing several new libraries, enhancing performance, security, and compatibility.

[coderabbitai]

Walkthrough

The update modifies the dependency configuration in source/TestAdapter/packages.lock.json by adding several new dependency entries. The changes introduce new libraries from the .NET framework, including a version update for System.Net.Http and additional entries for System.IO, System.Runtime, various System.Security.Cryptography packages, System.Text.Encoding, and threading libraries. Each dependency entry includes a specified version and content hash, and many list sub-dependencies that extend the overall dependency graph.

Changes

File Path	Change Summary
source/TestAdapter/.../packages.lock.json	Added new dependency entries: - System.Net.Http (v4.3.4) - System.IO, System.Runtime, System.Text.Encoding, System.Threading, System.Threading.Tasks (v4.3.0 each) - Security-related libraries: System.Security.Cryptography.Algorithms, Cng, Csp, Encoding, OpenSsl, Primitives, X509Certificates (v4.3.0 each), each with content hashes and sub-dependencies.

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 40e6142 and 5553a7f.

⛔ Files ignored due to path filters (2)

• source/TestAdapter/NanoCLRHelper.cs is excluded by none and included by none
• source/TestAdapter/nanoFramework.TestAdapter.csproj is excluded by none and included by none

📒 Files selected for processing (1)

• source/TestAdapter/packages.lock.json (11 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: nanoFramework.TestFramework (Build_Test_Framework)
• GitHub Check: nanoFramework.TestFramework (Get_Build_Flags)

🔇 Additional comments (2)

source/TestAdapter/packages.lock.json (2)

59-67: .NETFramework (v4.8) Dependency Updates for HTTP Client Migration
This update injects several new dependencies into the .NETFramework,Version=v4.8 section. In particular:

• "System.Net.Http" (lines 59–67, version 4.3.4): Essential for the new HTTP client functionality.
• "System.IO" (lines 103–107) and "System.Runtime" (lines 136–140): Likely required to support enhanced IO and runtime operations needed by the new client.
• Cryptography-related libraries (lines 154–183): New entries for "System.Security.Cryptography.Algorithms", "System.Security.Cryptography.Encoding", "System.Security.Cryptography.Primitives", and "System.Security.Cryptography.X509Certificates" are added. These ensure that cryptographic operations (e.g., handling certificates for secure HTTP communication) are adequately supported.

Please verify that the specified versions (e.g. 4.3.4 for System.Net.Http and 4.3.0 for the others) meet your platform compatibility and security requirements.

Also applies to: 103-107, 136-140, 154-164, 165-169, 170-174, 175-183

---

252-285: net6.0 Dependency Graph Expansion for HTTP Client Migration
The net6.0 section now includes a comprehensive set of new and updated dependency entries. Highlights include:

• "System.Net.Http" (lines 252–285): Updated for the migration to the new HTTP client with an extensive list of sub-dependencies (e.g. platform primitives, globalization, IO, and cryptography libraries).
• Platform-Specific and Runtime Dependencies:
  • Several runtime-specific native dependencies (e.g. for Debian, Fedora, OpenSUSE, macOS, RHEL, Ubuntu) have been added or updated (lines 310–324, 415–424, 425–444). These ensure that the application behaves correctly across different OS distributions.
  • Updates related to native support for system libraries such as "runtime.native.System", "runtime.native.System.Net.Http", and cryptographic providers (lines 340–369 and 370–394) provide the low-level functionality needed for robust HTTP communications.
• Additional Core Library Updates:
  A wide array of additional libraries (covering collections, diagnostics, globalization, IO, reflection, runtime, threading, etc.) are now specified (lines 445–887). These updates collectively expand and modernize the dependency graph to support the enhanced HTTP functionality and ensure overall platform compatibility.

Given the extensive expansion and interconnection of dependencies in the net6.0 target, please review these version constraints carefully to ensure they integrate smoothly into your build and runtime environments. It’s highly recommended to run thorough integration and compatibility tests on all target platforms to catch any potential conflicts.

Also applies to: 291-295, 310-314, 315-319, 320-324, 340-348, 361-369, 370-377, 378-394, 395-399, 400-404, 415-419, 420-424, 425-429, 430-434, 435-439, 440-444, 445-454, 455-471, 477-486, 487-498, 499-508, 509-518, 519-529, 530-542, 543-554, 555-569, 570-577, 586-597, 598-608, 609-620, 626-635, 636-647, 648-656, 657-666, 667-676, 677-689, 690-700, 710-730, 731-748, 749-768, 769-787, 788-807, 808-821, 822-853, 859-868, 869-877, 878-887

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.