Category: Aspire

  • Aspire Resource for Aspire–part 3–usage

    AspireExtensionsResource This package provides Aspire as a Resource in the Aspire Host Dashboard, making it easier to test and manage Aspire dashboards. You can download the solution at https://github.com/ignatandrei/aspireExtensions/tree/main/src/AspireResourceExtensions in order to see the tests. Installation Install via NuGet: Usage Add the Aspire resource to your distributed application builder: Use the resource to add environment…

  • Aspire Resource for Aspire–part 2–code

    So those are the challenges Challenge 1: Extracting the Dashboard URL The Aspire dashboard doesn’t expose its URL directly through a simple API. Instead, the URL is logged to the application’s output. To capture it, I had to hook into the logging infrastructure. I created a FakeLoggerProvider(https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.testing.fakeloggerprovider?view=net-9.0-pp) that collects log messages, then scanned those messages…

  • Aspire Resource for Aspire–part 1–idea

    I have published many  Aspire Extensions ( see https://msprogrammer.serviciipeweb.ro/category/aspire/ –  ) However, to make an AUTOMATED demo, I need the token url of the dashboard and the url itself. How can I obtain those and pass to the demo / tests ? So here are the specs As a Aspire Resource developer I wanted to…

  • WebApi SDK generator–part 2–naive implementation

    The decision to implement were: https://github.com/OpenAPITools/openapi-generator – because has multiple language implementations has a WebAPI docker Implement one SDK generator per WebAPI – it is simpler to generate commands for each one , rather to have multiple on the same ASPIRE resource Can wait for 1 WebAPI to become available, rather for all This said,…

  • WebApi SDK generator–part 1–idea

    In those days, every Web Project has 2 parts  – an API and an SPA . If we document the SPA for the users, the API is directed more to programmers- and it will be helpfull to have already generated for them SDK for the language of their choice. There are many generators in the…

  • Dotnet Global Tools Extension for ASPIRE–part 2–code and usage

    First thing – – usage must be simple . So this is something that can be reproduces easy on each ASPIRE project : builder.AddDotnetGlobalTools(“dotnet-ef”, “dotnet-depends”); I cannot imagine simpler than this  – and , of course, you can add many more other dotnet tools –  see https://www.nuget.org/packages?q=&includeComputedFrameworks=true&packagetype=dotnettool&prerel=true&sortby=relevance  What happens: Now a Aspire resource will be…

  • Dotnet Global Tools Extension for ASPIRE–part 1–idea

    Every time I am at a new PC , I need dotnet to program. Ans also I find the need to install some dotnet tools ( global or local) . To mention only 2, dotnet-ef – Entity Framework Core command-line tool for database scaffolding ,migrations and management dotnet-outdated – Checks for outdated NuGet dependencies in…

  • BlazorExtensionsAspire – integrate BlazorWebAssembly with WebAPI via Aspire–code

    BlazorExtensionsAspire solves the problem of automatically injecting the URL of WebAPI into Blazor WebAssembly . The code for obtaining writes into appsettings.json of BlazorWebAssembly To use it add this to a Aspire AppHost project and then add this to a BlazorWebAssembly project and then inject Do not forget to add CORS to webAPI !

  • BlazorExtensionsAspire – integrate BlazorWebAssembly with WebAPI via Aspire–idea

    Any WebAPI application needs an UI – and Blazor is a choice nowadays ( along other SPA , like Angular, React, Svelte … ) For integrating in ASPIRE ,there is a no simple task : Blazor should know the WebAPI url and use it to gather data. But the WebAPI URL could change  – so…

  • TestExtensionsAspire- part 2- execution

    Now the code mans to create commands about running dotnet <test or run> in the current folder of the csproj test project. Things that needed to be solved: 1.    Test Project as NuGet Package The main project (.csproj)  , that will be referenced as a NuGet dependency, it’s not an Aspire project, so it doesn’t…