When you find some @daprdev.bsky.social containers from two centuries ago 😊

(This is actually a known Docker CLI issue)

Some cool new stuff in @jetbrains.com Rider added in the latest update!

Dag Easypark! Gebruik de @anwbverkeer.bsky.social onderweg app wel.

Wanneer ga jij eerlijk toegeven dat je hier enkel bent om dit soort nepreacties te plaatsen?

As soon as we make this change, our AppHost stops complaining! Our AppHost can find the constant class and is now able to use its values. Thanks to this, changes to the values now only have to be made in one place and we can completely eliminate magic strings from our orchestration.

Luckily, the fix is easy. We open up the AppHost .csproj file and make an edit to the projectreference to the constants project.

When we add this class library as a project dependency to our AppHost project, that works well. Until we actually try to use the constants! Whoops!

We create a simple class library with a constants class that contains some static strings with our values.

In the project that consumes the database, we now use an extension method provided by the Aspire.Microsoft.EntityFrameworkCore.SqlServer NuGet package. Note that we need the name of the SQL database resource created earlier.

The code sets up our EF Core DbContext with the connection string.

When we run the AppHost, you can see the connection string being provided to the running project (which is just an ASP.NET Core web API).

We can reference the SQL Server database using the .WithReference(sql) method. This injects the connection string to the database into the environment variables of the service.

Other dependencies, such as a SQL Server database, can be defined in code.

When creating your AppHost in Aspire, you can create resources from your projects by adding the projects as a dependency to your AppHost.