WestyxNexus package is hosted on the GitLab Package Registry. It is public - no token is required to install.
1. Add the NuGet source
Choose one of the two options below. Both achieve the same end result.Option A - CLI (one-time, machine-wide)
NuGet.Config. After this the source is available in every project on the machine.
Option B - nuget.config in your repo root
.csproj. The source is then scoped to the project - no machine-wide setup needed.
2. Install the packages you need
The SDK ships as six packages. The core is always required; add only the integrations you use.
A typical ASP.NET Core application needs two, each of which brings in the core package -
Getting started wires them:
<PackageReference> to your .csproj pulling the latest version from the GitLab feed.
To pin to a specific version:
Requirements
- .NET 10.0 or later. All six packages target
net10.0(LTS, supported to 2028-11-14).net8.0reached end of support on 2026-11-10 and was dropped inv0.21.0. CI runs the suite on .NET 10 and forward-tests thenet10.0build on .NET 11. - Network access to
gitlab.comfor installation, and to<your-slug>.westyx.devat runtime
Verifying connectivity
Before writing any code, confirm your endpoint and API key work with a plaincurl:
configs, secrets, and flags. An HTTP 401 means the key is wrong; HTTP 404 means the slug is wrong.
To watch the live SSE stream:
event:resync arrive within a second. Press Ctrl+C to stop.
Troubleshooting
Unable to load the service index for source ...- usually a corporate proxy or firewall blocking GitLab. Confirmcurl https://gitlab.com/api/v4/projects/81978985/packages/nuget/index.jsonreturns JSON.The package version 'X' could not be found- version not yet published, or the GitLab feed is being rebuilt. Check the Packages page for the available versions.- Multiple feeds returning the same package - NuGet uses the first feed where the package is found. Order matters in
nuget.config. Putwestyx-nexusabove any catch-all feed.
