Projects in this Workspace

FakeLogger demo

• Location: apps/fakelogger-demo (app) and apps/fakelogger-demo.Test (tests).
• Purpose: demonstrates capturing and asserting on ILogger output from MyService in unit tests. MyService logs a start message and a "Work done" message with a structured Result value (expected value: 42).
• Test approach: the tests use the official testing helpers from the Microsoft.Extensions.Diagnostics.Testing package (exposed under Microsoft.Extensions.Logging.Testing) — specifically FakeLogger<T> and FakeLogRecord — to collect emitted log records and assert on level, message and structured state.

How to run the demo tests locally (PowerShell):

# run tests for the fakelogger demo
dotnet test .\apps\fakelogger-demo.Test\fakelogger-demo.Test.csproj --no-restore --verbosity minimal

Notes:

• Ensure you have a .NET SDK compatible with the projects' TargetFramework (check the projects' csproj files).
• If you modify logging or test packages, run dotnet restore before running dotnet test.
• The repository previously included a local FakeLogger shim during iteration; tests now use the official Microsoft.Extensions.Diagnostics.Testing helpers. If tests fail, verify the test project's package references and the project reference to the app are intact.

Angular and dotnet fastendpoint combination

Considering #240, there is a 2 part project, namely dotnet-fe-auth and angular-auth-example that represent the option that would normally be a dotnet new creation, namely dotnet new angular -o Project. However, this is a project that would be intertwined with controllers and an old angular version, which makes it hard to maintain both. Second, there is no real interaction between the two itself... you have to still create the services to call the controller api. This combination has nswag in between, creating said interaction.

dotnet-fe-auth

dotnet-fe-auth is a .NET backend project that provides authentication services using JWT tokens. It includes endpoints for validating tokens and integrates with FastEndpoints for rapid API development. The project is configured to use symmetric key encryption for JWT tokens.

Key Features:

• JWT Authentication
• Token Validation Endpoint
• FastEndpoints Integration
• Swagger Documentation

How to Run:

1. Navigate to the dotnet-fe-auth directory.
2. Run dotnet build to build the project.
3. Run dotnet run to start the server.
4. The server will be available at https://localhost:5001.

angular-auth-example

angular-auth-example is an Angular frontend project that demonstrates authentication using JWT tokens. It includes a login form, protected routes, and integration with the dotnet-fe-auth backend for token validation.

Key Features:

• Login Form
• JWT Token Storage in LocalStorage
• Protected Routes with Angular Guards
• HTTP Interceptor for Adding JWT Token to Requests

How to Run:

1. Before ever running, make sure you ran the npm run dev-cert command in the root of the repository to generate a development certificate.
2. Run npx nx serve angular-auth-example to start the development server.
3. The application will be available at https://localhost:4200.

This app is dependant on the dotnet-fe-auth backend project to be running in order to authenticate users and validate tokens.