This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm working on a .NET 8 project to learn how to use minimal APIs, in the same project, that includes Blazor components. I don't know how to consume the minimal API in the project, so I asked Bing Copilot how to do that. In part, this is what it gave me that I should put into the Program.cs file:
builder.Services.AddRazorComponents();
builder.Services.AddScoped(sp => new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });
However, Visual Studio 2022 complains about builder.HostEnvironment.BaseAddress. It says:
CS1061 'WebApplicationBuilder' does not contain a definition for 'HostEnvironment' and no accessible extension method 'HostEnvironment' accepting a first argument of type 'WebApplicationBuilder' could be found (are you missing a using directive or an assembly reference?
My guess is that section of code was valid in an older version of .NET but is no longer correct. I've tried rephrasing the question multiple times, but Bing Copilot continues to give me that code. So, my question is what should I use?
The code you've shared is for Blazor Client Side. Replace the code with the following to make HTTP calls from the server.
builder.Services.AddHttpClient();
That brings up the question why are you adding minimal API?
I think your general design approach is a little shaky. Can you clarify the general design goals?
I'm using minimal API because it is a technology I wan to explore. And the app I'm working on a simple enough that it won't have a lot of API endpoints, otherwise I'd use a MVC API approach instead.
Blazor Server Side and minimal API have the same access to server resources. In your setup minimal API is redundant because Blazor server side can execute the same logic as minimal API.
You could have other plans for minimal API. That's why I asked for the design goals. I did not want to jump to conclusions.
I think a better learning path is creating a separate minimal API project because making an HTTP call from Server A to Server B makes sense. Your current configuration would make an HTTP call to and from the same server application. While this works, it would be easier, less code, and less clock cycles for Blazor Server Side to execute the logic.