Skip to content

Organize SDK projects in solution - #5720

Closed
Brendan Kowitz (brendankowitz) wants to merge 1 commit into
microsoft:mainfrom
brendankowitz:brendankowitz-fix-sdk-solution-folders
Closed

Organize SDK projects in solution#5720
Brendan Kowitz (brendankowitz) wants to merge 1 commit into
microsoft:mainfrom
brendankowitz:brendankowitz-fix-sdk-solution-folders

Conversation

@brendankowitz

@brendankowitz Brendan Kowitz (brendankowitz) commented Aug 11, 2026

Copy link
Copy Markdown
Member

Description

Organizes the four Firely SDK projects and the Ignixa provider project beneath a src > SDK solution folder. This improves solution navigation only; project definitions, GUIDs, build configuration, packages, and runtime behavior are unchanged.

This change does not require corresponding PaaS changes.

Related issues

Addresses AB#198706.

Testing

  • dotnet sln Microsoft.Health.Fhir.sln list
  • git diff --check origin/main...HEAD

FHIR Team Checklist

  • PR title is succinct and under 65 characters.
  • Tagged as Enhancement and Open source.
  • No SQL scripts were added or changed.
  • No ADR is required because this does not change system behavior or design assumptions.
  • CI is green before merge Build Status
  • Reviewed squash-merge requirements.

Semver Change (docs)

Skip — solution-folder organization only; no shipped behavior or package changes.

Group Firely SDK and Ignixa provider projects under src/SDK for easier discovery without changing project definitions or build configuration.

Changes:
- Microsoft.Health.Fhir.sln: Add the SDK solution folder and reparent five SDK-related projects.

Tools: skill: codeblend-commit

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Visual Studio solution structure to group the Firely SDK projects and the Ignixa provider project under a new src > SDK solution folder, without changing project identities (paths/GUIDs) or build configurations.

Changes:

  • Added a new solution folder named SDK under the existing src solution folder.
  • Moved the Firely SDK projects (Stu3/R4/R4B/R5) and Microsoft.Health.Fhir.Ignixa into the SDK solution folder via NestedProjects mappings.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@brendankowitz Brendan Kowitz (brendankowitz) added Enhancement Enhancement on existing functionality. Open source This change is only relevant to the OSS code or release. No-PaaS-breaking-change No-ADR ADR not needed labels Aug 11, 2026
@brendankowitz

Copy link
Copy Markdown
Member Author

Superseded by #5721, recreated from a branch on microsoft/fhir-server so the ADO PR pipeline has access to service connections and Key Vault secrets (fork PRs skip those tasks).

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

Labels

Enhancement Enhancement on existing functionality. No-ADR ADR not needed No-PaaS-breaking-change Open source This change is only relevant to the OSS code or release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants