Skip to content

Add support for slnx projects#434

Open
Ellerbach wants to merge 1 commit intomainfrom
support-slnx
Open

Add support for slnx projects#434
Ellerbach wants to merge 1 commit intomainfrom
support-slnx

Conversation

@Ellerbach
Copy link
Copy Markdown
Member

@Ellerbach Ellerbach commented Apr 3, 2026

Description

Add support for slnx projects

Motivation and Context

  • Add support for slnx projects

How Has This Been Tested?

Tested locally

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

  • Extended nanoFramework commands (build, deploy, add, package management utilities) to recognize .slnx file extension in VS Code context menus, expanding compatibility beyond .sln and .nfproj files.

@nfbot nfbot added Type: enhancement New feature or request Type: Documentation Improvements or additions to documentation labels Apr 3, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 3, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a53f6cf0-8127-4ed9-a89e-226069ba572b

📥 Commits

Reviewing files that changed from the base of the PR and between c2db12d and 5c24b92.

⛔ Files ignored due to path filters (7)
  • README.md is excluded by !**/*.md and included by none
  • installation.md is excluded by !**/*.md and included by none
  • src/debugger/nanoDebugSession.ts is excluded by none and included by none
  • src/debugger/types/debugTypes.ts is excluded by none and included by none
  • src/dotnet.ts is excluded by none and included by none
  • src/extension.ts is excluded by none and included by none
  • src/utils.ts is excluded by none and included by none
📒 Files selected for processing (1)
  • package.json

Walkthrough

Updates VS Code context menu when conditions in package.json to recognize .slnx file extension for six nanoFramework commands (nfbuild, nfdeploy, nfadd, nfaddnuget, nfremovenuget, nfupdatenuget), expanding their applicability beyond .sln and .nfproj files.

Changes

Cohort / File(s) Summary
VS Code Context Menu Configuration
package.json
Added resourceExtname == .slnx condition to context menu when clauses for six nanoFramework commands, enabling command visibility and eligibility for .slnx files in addition to existing .sln and .nfproj extensions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add support for slnx projects' accurately describes the main change in the pull request, which is to extend VS Code command context menu conditions to recognize the .slnx file extension.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch support-slnx

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Documentation Improvements or additions to documentation Type: enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants