Improve root namespace for vxproj files

[networkfusion]

Description

Fixes the root VS CPP project namespaces used when creating new source files in VC++ project.

Motivation and Context

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)
• Dev Containers (changes related with Dev Containers, has no impact on code or features)
• Dependencies/declarations (update dependencies or assembly declarations and changes associated, 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).

Summary by CodeRabbit

• Refactor
  • Streamlined module categorization across networking, time synchronization, GPIO, and serial communication components to align with updated nanoFramework standards, ensuring a more consistent framework experience.

[coderabbitai]

Walkthrough

The changes update the RootNamespace property in four project files (.vcxproj). Each file’s previous value of "Windows.Storage" is replaced with a nanoFramework-specific namespace that indicates a shift in the module’s framework affiliation. No other modifications were made to the project configurations, item groups, or file structures.

Changes

File(s)	Change Summary
src/DeviceInterfaces/.../Networking.Sntp.vcxproj src/DeviceInterfaces/.../System.Net.vcxproj	Updated "RootNamespace" from "Windows.Storage" to "nanoFramework.Networking.Sntp" (Networking.Sntp) and "nanoFramework.Networking" (System.Net) respectively.
src/.../System.Device.Gpio.vcxproj src/.../System.IO.Ports.vcxproj	Updated "RootNamespace" from "Windows.Storage" to "nanoFramework.System.Device.Gpio" (System.Device.Gpio) and "nanoFramework.System.IO.Ports" (System.IO.Ports) respectively.

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/DeviceInterfaces/System.Net/System.Net.vcxproj (1)

40-40: Consider aligning namespace with directory structure.

The namespace nanoFramework.Networking doesn't match the project's directory name System.Net. For consistency with other projects and to avoid confusion, consider using nanoFramework.System.Net instead.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d2c2a50 and a3a82c5.

📒 Files selected for processing (4)

• src/DeviceInterfaces/Networking.Sntp/Networking.Sntp.vcxproj (1 hunks)
• src/DeviceInterfaces/System.Net/System.Net.vcxproj (1 hunks)
• src/System.Device.Gpio/System.Device.Gpio.vcxproj (1 hunks)
• src/System.IO.Ports/System.IO.Ports.vcxproj (1 hunks)

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

• GitHub Check: nf-interpreter (Nightly build) (Build_STM32_targets ST_NUCLEO64_F091RC)
• GitHub Check: nf-interpreter (Nightly build) (Build_STM32_targets ORGPAL_PALX)
• GitHub Check: nf-interpreter (Nightly build) (Build_STM32_targets ORGPAL_PALTHREE)
• GitHub Check: nf-interpreter (Nightly build) (Check_Build_Options)

🔇 Additional comments (3)

src/System.IO.Ports/System.IO.Ports.vcxproj (1)

31-31: LGTM! Namespace change aligns with project structure.

The new namespace nanoFramework.System.IO.Ports correctly reflects the project's directory structure and purpose.

src/DeviceInterfaces/Networking.Sntp/Networking.Sntp.vcxproj (1)

31-31: LGTM! Namespace change aligns with project structure.

The new namespace nanoFramework.Networking.Sntp correctly reflects the project's directory structure and purpose.

src/System.Device.Gpio/System.Device.Gpio.vcxproj (1)

32-32: LGTM! Namespace change aligns with project structure.

The new namespace nanoFramework.System.Device.Gpio correctly reflects the project's directory structure and purpose.

[josesimoes]

Nice catch! Thank you. 👍🏻