aspnetcore

If you list the Router's AppAssembly the AdditionalAssemblies property then you get somewhat bizarre errors when you load the app.

<Router AppAssembly="@typeof(App).Assembly"
    AdditionalAssemblies="new[]{typeof(App).Assembly}">
   ...

This is what you see in a Blazor WebAssembly app in the browser console logs:

blazor.webassembly.js:1 
        
       crit: Micro

I followed the tutorial to the letter, and while the client displayed the correct results in the console,
the server did not display any information that it received a client request.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1d298a6c-8ddc-dbc8-d219-0fa7138442c2
• Version Independent ID: b96be346-958a

Hi,

my admin portal looks like this :

Version

• Server Installed 1.38.4
• Server Latest 1.38.4
• Web Installed -
• Web Latest 2.17.1

It seems that, at some point, 'GetInstalledWebVersion()' in 'Admin.dll' is called? Could anyone help me understand what do I need to check, to fix this?

Seem we need RemoveAll cache with out parameter, or can called by remove everything for invalidate all cache.

For now I use following code

var listPrefix = new List<string>
{
    "foo",
    "bar",
    "another-foo"
};

listPrefix.ForEach(prefix => {
   cachingProvider.RemoveByPrefix(prefix);
});

Instead of write above code, we may can write single like below

` cachin

Beyonce said it best. If you like it then you shoulda put a test on it. Scenarios I like:

• Cert is created with right DN
• Cert is stored to X509Store after creation
• Cert request is not resubmitted
• Handles failures gracefully
• HTTP challenge/response works as expected
• Certificate renewal when cert is about to expiration