Skip to content

fix(solution): register missing Quota project in FSH.Starter.slnx (resolves NU1105)#1296

Open
sabinshrestha wants to merge 1 commit into
fullstackhero:mainfrom
sabinshrestha:fix/project_startup
Open

fix(solution): register missing Quota project in FSH.Starter.slnx (resolves NU1105)#1296
sabinshrestha wants to merge 1 commit into
fullstackhero:mainfrom
sabinshrestha:fix/project_startup

Conversation

@sabinshrestha

Copy link
Copy Markdown

Summary

Fixes a NU1105 restore cascade that breaks dotnet restore and Visual Studio's open of src/FSH.Starter.slnx on a fresh clone.

src/BuildingBlocks/Quota/Quota.csproj exists on disk and is referenced via <ProjectReference> from several projects (Storage, Web, Framework.Tests, Modules.Billing), but it was never added to the solution. NuGet restore therefore can't walk the project graph and emits NU1105 for every project that depends on those four — which cascades to nearly every module, host, and test project.

Root cause

src/FSH.Starter.slnx was missing the entry below under the /BuildingBlocks/ folder:

<Project Path="BuildingBlocks/Quota/Quota.csproj" />

Fix

Added the Quota project to the solution in its alphabetical position (between Persistence and Shared).

Verification

  • dotnet restore src/FSH.Starter.slnx → "All projects are up-to-date for restore."
  • Visual Studio Error List: all NU1105 entries gone after reopening the solution.

Suggested follow-up (out of scope for this PR)

Add a CI check that every <ProjectReference>-referenced .csproj is a member of FSH.Starter.slnx, so this kind of drift is caught automatically. A small script that diffs dotnet sln list against the union of all ProjectReference paths would do it.

Added Quota.csproj to solution with Debug build config.
Marked multiple dependencies as peer in package-lock.json.
Updated some package versions (e.g., react, vite).
@sabinshrestha

Copy link
Copy Markdown
Author

Issue Fixes #1291

@sabinshrestha sabinshrestha mentioned this pull request Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants