Skip to content

Fix startup plugin paths for issue #331#354

Closed
csharpfritz wants to merge 1 commit into
FritzAndFriends:v0.7from
csharpfritz:issue-331-content-root-paths
Closed

Fix startup plugin paths for issue #331#354
csharpfritz wants to merge 1 commit into
FritzAndFriends:v0.7from
csharpfritz:issue-331-content-root-paths

Conversation

@csharpfritz

Copy link
Copy Markdown
Contributor

Summary

  • anchor plugin-system paths to the ASP.NET Core content root through SharpSitePathProvider
  • initialize PluginManager path resolution from the web app content root so default plugin installation works during OOTB setup
  • add regression coverage ensuring Step2 does not directly inject IHandleFileStorage

Testing

  • dotnet test .\tests\SharpSite.Tests.Plugins\SharpSite.Tests.Plugins.csproj --nologo --verbosity minimal
  • dotnet test .\tests\SharpSite.Tests.Web\SharpSite.Tests.Web.csproj --nologo --verbosity minimal

Anchor plugin-system paths to ASP.NET Core content root so default plugin installation, application state persistence, and plugin asset resolution work during out-of-box startup from upstream v0.7.

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

Copy link
Copy Markdown
Contributor Author

Closed as duplicate of #353. Both PRs implement identical solutions for issue #331. #353 is canonical with more comprehensive documentation.

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.

1 participant