To build from command line (specifically PowerShell on Windows):

Quick publish (recommended): Publish-Scheduler.ps1

The easiest way to publish everything is the Publish-Scheduler.ps1 script in the repository root. From a PowerShell prompt in the repo root, run:

.\Publish-Scheduler.ps1

This publishes the API (which bundles the Blazor WASM frontend), the Service, and the ServiceChecker in Release configuration, producing two flavors of each:

• framework-dependent — smaller output that requires .NET 10.0 to be installed on the target machine.
• self-contained (win-x64) — larger output that bundles the .NET runtime, so the target machine does not need .NET installed.

The output is written to C:\Scheduler_Publish, laid out as:

C:\Scheduler_Publish\
    framework-dependent\
        SimpleSchedulerAPI\
        SimpleSchedulerService\
        SimpleSchedulerServiceChecker\
    win-x64-self-contained\
        SimpleSchedulerAPI\
        SimpleSchedulerService\
        SimpleSchedulerServiceChecker\

Note: the script deletes and recreates C:\Scheduler_Publish on each run. To publish to a different location, edit the $PublishDir variable at the top of the script.

Copy the project folder you want from the appropriate flavor to your server and install it as a Windows Service (see the per-project sections below for the New-Service / sc.exe commands).

The sections below document publishing each project individually, which is useful for development or if you only need to deploy one piece.

API (also hosts the Blazor WASM frontend):

dotnet publish .\SimpleSchedulerAPI\ --configuration Release

This will put your output into .\SimpleSchedulerAPI\bin\Release\net10.0\publish\.

The API project references SimpleSchedulerBlazorWasm, so the WASM static files are copied into wwwroot/ automatically and served by the same process.

Running as a Windows Service

The API is configured to run either as a console app (during development) or as a Windows Service (in production) — Host.UseWindowsService() detects which.

1. Publish the project (see above) and copy the publish folder to your server, for example C:\Services\SimpleSchedulerAPI.

2. Set the listen URL in appsettings.json ("Urls": "http://+:5266" to bind on all interfaces, or pick whatever host/port you want). Configure connection strings, JWT settings, etc. in the same file.

3. Open an elevated PowerShell prompt and run:

   New-Service -Name SimpleSchedulerAPI `
       -BinaryPathName "C:\Services\SimpleSchedulerAPI\SimpleSchedulerAPI.exe" `
       -DisplayName "Simple Scheduler API" `
       -Description "Simple Scheduler API and Blazor WASM frontend" `
       -StartupType Automatic
   # Optional: run under a specific account so it has rights to SQL / the
   # workers folder. Add: -Credential (Get-Credential MyDomain\MyUser)
   
   Start-Service SimpleSchedulerAPI

   Or with sc.exe:

   sc.exe create SimpleSchedulerAPI binPath= "C:\Services\SimpleSchedulerAPI\SimpleSchedulerAPI.exe" start= auto DisplayName= "Simple Scheduler API"
   sc.exe description SimpleSchedulerAPI "Simple Scheduler API and Blazor WASM frontend"
   sc.exe start SimpleSchedulerAPI

4. To uninstall:

   Stop-Service SimpleSchedulerAPI
   Remove-Service SimpleSchedulerAPI   # or: sc.exe delete SimpleSchedulerAPI

The service account needs:

• Permission to bind the configured URL (http://+:port requires either admin rights or a netsh http add urlacl reservation).
• Read/write access to the workers folder and any log paths in appsettings.json.
• SQL access (Windows auth uses the service account; otherwise put the credentials in the connection string).

If you want HTTPS, configure a Kestrel:Endpoints:Https block in appsettings.json with a certificate, or put a reverse proxy (IIS, nginx, YARP) in front of the service. By default the app listens on plain HTTP only; the UseHttpsRedirection middleware is a no-op until an HTTPS endpoint exists.

-- TODO: Add instructions for running this in Mac or Linux

Blazor WASM (standalone hosting — optional):

The WASM frontend ships inside the API service by default, so no separate hosting is required. If you would rather host the static files on their own (CDN, static site, separate web server), publish the project directly:

dotnet publish .\SimpleSchedulerBlazorWasm\ --configuration Release

This puts the static output in .\SimpleSchedulerBlazorWasm\bin\Release\net10.0\publish\wwwroot\. Point that deployment at your API by editing wwwroot/appsettings.json (ApiUrl).

Service:

dotnet publish .\SimpleSchedulerService\ --configuration Release

This will put your output into .\SimpleSchedulerService\bin\Release\net10.0\publish\.

Copy the output to your server and install as a Windows Service:

New-Service -Name SimpleScheduler `
    -BinaryPathName "C:\Services\SimpleSchedulerService\SimpleSchedulerService.exe" `
    -DisplayName "Simple Scheduler" `
    -Description "Simple Scheduler job runner" `
    -StartupType Automatic
Start-Service SimpleScheduler

-- TODO: Add instructions for running this in Mac or Linux

ServiceChecker:

dotnet publish .\SimpleSchedulerServiceChecker\ --configuration Release

This will put your output into .\SimpleSchedulerServiceChecker\bin\Release\net10.0\publish\.

Install as a Windows Service the same way:

New-Service -Name SimpleSchedulerChecker `
    -BinaryPathName "C:\Services\SimpleSchedulerServiceChecker\SimpleSchedulerServiceChecker.exe" `
    -DisplayName "Simple Scheduler Checker" `
    -Description "Simple Scheduler health checker" `
    -StartupType Automatic
Start-Service SimpleSchedulerChecker

-- TODO: Add instructions for running this in Mac or Linux

SQL Server:

You can publish from the Visual Studio SimpleSchedulerSqlServerDB.publish.xml file, or create the objects manually.

You'll need to add an email address to the Users table manually.

Run this:

ALTER DATABASE [TheDatabaseName] SET ALLOW_SNAPSHOT_ISOLATION ON;

-- TODO: Provide instructions or at least a link for running SQL Server from Docker

-- TODO: Make a better SQL Server install script

-- TODO: More instructions on how to use scheduler

-- TODO: On start of API, create account for AdminEmail (from config file) in database if it doesn't already exist