We're several versions of .NET behind. The develop branch is in a weird state of a .NET upgrade mixed with hacked together csproj modifications to allow Blazor and Razor pages to be embedded in plugins which may complicate future upgrades or add unintended side effects.
To that end, I think we should open this new issue, start a new branch, and perform a fresh upgrade to .NET 10 and only using master/develop as a reference and either try to implement a razor pages solution that does not require all of this hackery or implement another .NET-centric web UI solution for plugins.
The goals of this issue are...
- Upgrade the host to .NET 10.
- Provide a way for plugin authors to expose endpoints on the host's web server.
- Integrate a plugin manager/marketplace directly within the host utilizing the web server as a configuration and management engine.
-
- Plugin manager/marketplace should allow for...
-
-
- Hot load/unload of plugins.
-
-
-
- Downloading of new plugins.
-
-
- Removal of existing plugins.
-
-
- Display of each currently loaded plugin's registered endpoints.
We're several versions of .NET behind. The develop branch is in a weird state of a .NET upgrade mixed with hacked together csproj modifications to allow Blazor and Razor pages to be embedded in plugins which may complicate future upgrades or add unintended side effects.
To that end, I think we should open this new issue, start a new branch, and perform a fresh upgrade to .NET 10 and only using master/develop as a reference and either try to implement a razor pages solution that does not require all of this hackery or implement another .NET-centric web UI solution for plugins.
The goals of this issue are...