razor | A google 's congestion Control Algorithm | Proxy library

You need to include the using statement, either in the component.razor file, or in _Imports.razor (preferred if you are going to be using JSInterop often):

The connection string should be configured in the same project where the services connect to the DbContext, so you can leave the appsettings.json as-is.

It is the configuring project (the one that is setting up all the dependencies) that sets the connection to the DB, and the EF migration tool needs the connection to track and apply changes. Any assembly can be used to store migrations, but the EF tool needs to be invoked for a project with an actual connection.

EF Core uses Dependency Injection to configure services for runtime which includes setting the connection string for any DB. The control of how the DB classes interact with their environment is given to the app that is running it, which allows for the same DB code to be used across multiple instances, states and even providers. EF Core uses the current state & provider of the DB where it is deployed to determine changes and scaffolding, so it can only create migrations with a configured instance of a DbContext connected to a DB (usually the development instance).

When a solution is comprised multiple dependent services with a common data model that will need the same migrations, only one of the projects in the solution should be responsible for managing DB state. Whichever project is chosen, it needs to create a DBContext with a valid connection when it starts up for the EF tools to work. ASP.NET Core uses the Microsoft.Extensions.Configuration package and the UseStartup method to make the configuration simple. This can be your existing UI project that would read the connection string from existing settings and pass it to your CustomDbContext at Startup. The EF Tools CLI will use the default profile (the Green run arrow) to get the settings from launchSettings.json and appSettings.json to connect to the DB. The configuration should be in place in each environment you deploy to so that the migrations can be run from the same configuring project and applied as needed.

You can avoid ASP.NET and create a custom startup class in your data package that runs to apply migrations, but this is a lot of extra work for something already in the box. The DbContext class does have an OnConfiguring method that can be used to set the connection. Placing configuration inside of code limits where the software can run, so it should still be set externally.

The DbContext can be referenced from another package:

The DbContext and Models can be defined in a separate 'pure' project, then referenced in the Startup like so:

@ is its own escape character. Simply put in @@. Alternatively you can store the URL as a string variable and use that.

You can update the tooltip title by changing the data-bs-original-title attribute

Did you change the TargetFramework to 5.0?

You cannot apply a class to a Component. You can use splatting to capture attributes placed on a Component to pass as parameter to one of the components elements.

SomeComponent.razor

As far as I understood both your question and the Blazor concepts, the answer to your question is « no ». There is no possibility to retrieve statically the current HTTP context in Blazor. Because you never know if the context is an initial page load or just SignalR communication to update the current page. Here is the manner I save this situation:

• Create a cascading parameter that is shared by all razor components

• This cascading parameter is a class with many information coming from initial HTTP request, caught in the _Host.cshtml from the httpContextAccessor.HttpContext

• This cascading parameter class gets all the methods of my previous static methods.

• These methods can use the properties of the cascading parameter: RawUrl, UserAgent, ClientIp, …

This implies hard refactoring work to migrate legacy ASP web sites. But the performances of Blazor are worth it.

Here is a demo to get display name with enum value:

EnumExtensions:

First, I would highly recommend that you (or anyone using Cosmos DB .Net SDK) to watch this video on Cosmos DB Youtube Channel: https://www.youtube.com/watch?v=McZIQhZpvew. This provides really useful information about the best practices to follow when working with this SDK.

This video will explain why the first request takes so much time and how you can speed that up.

To summarize for the purpose of this answer, creating an instance of Cosmos Client (with "Direct" connection mode) does not do much. When you make the 1st request with that client, the initialization happens and at that time SDK makes a few network requests to get necessary information about establishing "Direct" (TCP) connection. That's why it takes a great deal of time with the 1st request. After the 1st request, the information is cached by the SDK so subsequent requests take much less time than the 1st one.

To do the initialization while creating Cosmos client, you would need to use CreateAndInitializeAsync method of the CosmosClient. Here's an example of the same from the documentation page: