Files
oqtane.framework/Oqtane.Application
Leigh Pointer 783d01bf9f Rename client and server module services
Rename the client service class to Client[Module]Service and the server service file to Server[Module]Service, updating all references accordingly. Updated DI registration in ClientStartup to register Client[Module]Service, and updated Edit.razor and Index.razor to inject and call Client[Module]Service instead of [Module]Service. This clarifies client vs server implementations and avoids naming collisions.
2026-02-06 18:31:58 +01:00
..
2025-12-30 13:43:11 -05:00
2025-08-19 12:26:54 -04:00
2025-08-17 10:53:22 -04:00
2025-09-25 14:46:51 -04:00

Oqtane Application Template

This is a Visual Studio Project Template designed for Oqtane development projects. This template relies on the native templating capabilities of the .NET Command Line Interface (CLI):

dotnet new install Oqtane.Application.Template
dotnet new oqtane-app -o MyCompany.MyProject
cd MyCompany.MyProject
dotnet build
cd Server
dotnet run
browse to Url

When using this approach you do not need to have a local copy of the oqtane.framework source code - you simply utilize Oqtane as a standard application dependency.

The solution also contains Client, Server, and Shared folders which is where you you would implement your custom functionality. An example module and theme are included for reference, and you can add additional modules and themes within the same projects by following the standard Oqtane folder/namespace conventions.

Known Issues

  • do not use the term "Oqtane" or "Module" in your output name or else you will experience namespace conflicts