profile
viewpoint
Mark Fayngersh pheuter New York https://www.markfayngersh.com co-founder & cto @CareSwitch. previously @quartethealth; @CrowdTwist; @mit

issue openedAzure/dev-spaces

Helm v3 Support

Now that it is officially out, would be great for azds to support it.

created time in 2 days

issue commentmicrosoft/vscode-react-native

Support for VS Code Remote Containers

@RedMickey Great, thanks!

ruslan-bikkinin

comment created time in 5 days

issue commentaspnet/AspNetCore

AspNetCore 3.0 Blazor Server inconsistent rendering between server and client of authorized components

This current discrepancy between local dev and prod is affecting the deployment of our application. Is there a reasonable workaround you can suggest, ideally with some code example that applies to this particular case?

I'm using Microsoft auth which automatically handles setting the claims for me, so I'm not exactly sure what you mean by applying transformers.

pheuter

comment created time in 10 days

issue commentaspnet/AspNetCore

AspNetCore 3.0 Blazor Server inconsistent rendering between server and client of authorized components

@javiercn Can you point me to an example of "apply a claims transformer"?

pheuter

comment created time in 11 days

issue openedMicrosoftDocs/vsonline

Default dotnet sdk set to LTS which breaks ASP.NET Core 3.0 apps

Looks like the default VS Online dotnet sdk is set to LTS [1] which breaks my ASP.NET Core 3.0 project in an interesting way. The initial startup Oryx build succeeds [2] but the Omnisharp dotnet restore command fails [3]. When I try to manually set /opt/dotnet/sdks/3.0 in .bashrc it still inserts the LTS version first in PATH.

[1] In default ~/.bashrc: PATH=$PATH:/opt/oryx:/opt/nodejs/lts/bin:/opt/dotnet/sdks/lts

[2]

Source directory : /home/vsonline/workspace

Using .NET Core SDK Version: 3.0.100

Restoring packages...

Welcome to .NET Core 3.0!

[3]

/opt/dotnet/sdks/2.1.802/sdk/2.1.802/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(137,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.0. Either target .NET Core 2.1 or lower, or use a version of the .NET SDK that supports .NET Core 3.0

created time in 12 days

issue commentaspnet/AspNetCore

AspNetCore 3.0 Blazor Server inconsistent rendering between server and client of authorized components

I've added some debug output to the Razor page to enumerate over all user claims using the code below. Something weird is happening where the initial server render contains the proper set of claims and the right issuer, and then when the client loads it switches all the issuers to LOCAL AUTHORITY and duplicates the claims.

Page.razor:

<AuthorizeView>
    <Authorized>
        @foreach (var claim in context.User.Claims)
        {
            <p>@claim.Type - @claim.Value Issued By @claim.Issuer</p>
        }
    </Authorized>
</AuthorizeView>

Server rendered: Server_rendered

Client rendered: Client_rendered

pheuter

comment created time in 12 days

issue commentaspnet/AspNetCore

AspNetCore 3.0 Blazor Server inconsistent rendering between server and client of authorized components

I should add that the same exact app works just fine in development. Can this have something to do with the fact that the production app uses Azure SignalR and for some reason that fails to read claims on the user session? Interesting enough, Azure SignalR is still able to tell that my user is logged in.

pheuter

comment created time in 12 days

issue openedaspnet/AspNetCore

AspNetCore 3.0 Blazor Server inconsistent rendering between server and client of authorized components

I am seeing a weird issue during the runtime of my ASP.NET Core 3.0 Blazor Server app where the prerendered page properly renders HTML inside of an <AuthorizeView Policy="Admin"> but quickly gets updated to render the <NotAuthorized> version once the browser client loads. I've attached a video demo below as well as the relevant source code. You can see the view flicker from the properly authorized view to the unauthorized one, even though the user remains logged in with the appropriate claims.

Demo

Demo

Source

In Startup.cs:

services.AddAuthorization(options =>
{
    options.AddPolicy("Admin", policy =>
    {
        policy.RequireAssertion(context => context.User.HasClaim(c => c.Issuer == "Microsoft"));
    });
});

In NavMenu.razor:

<AuthorizeView Policy="Admin">
    <Authorized>
        <NavLink href="/admin">Admin</NavLink>
    </Authorized>
</AuthorizeView>

In Admin.razor:

@page "/admin"
@attribute [Authorize(Policy = "Admin")]

<h3>Admin</h3>

created time in 12 days

issue commentBlazorExtensions/Logging

Some services are not able to be constructed

Yeah that's what I've already been using. Of course the regular ILogger goes to console and not the browser console, but that'll have to do for now.

moonolgerd

comment created time in 16 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server app does not start when adding browser logging

Noticed the blazor-wasm tag was added, just wanted to clarify that this is only an issue when using the Server hosted model. It appears to work fine when using wasm.

pheuter

comment created time in 17 days

issue commentBlazorExtensions/Logging

Some services are not able to be constructed

Yeah, so that was my intuition for the difference. I'm using Server so it makes sense for that to be a problem since IJSRuntime may need to log and the logger needs IJSRuntime to do the logging.

moonolgerd

comment created time in 17 days

issue commentBlazorExtensions/Logging

Some services are not able to be constructed

Are you using Blazor Server or Blazor Client with WebAssembly?

moonolgerd

comment created time in 17 days

issue commentBlazorExtensions/Logging

Some services are not able to be constructed

Using v1.0.0 which is the latest.

moonolgerd

comment created time in 17 days

issue openedaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server app does not start when adding browser logging

I'm trying to add the BlazorExtension.Logging library to my ASP.NET Core 3.0 application and I'm getting the following error that suggests some circular dependency issue between IJSRuntime and BrowserConsoleLogger:

System.AggregateException
  HResult=0x80131500
  Message=Some services are not able to be constructed
  Source=Microsoft.Extensions.DependencyInjection
  StackTrace:
   at Microsoft.Extensions.DependencyInjection.ServiceProvider..ctor(IEnumerable`1 serviceDescriptors, ServiceProviderOptions options)
   at Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider(IServiceCollection services, ServiceProviderOptions options)
   at Microsoft.Extensions.DependencyInjection.DefaultServiceProviderFactory.CreateServiceProvider(IServiceCollection containerBuilder)
   at Microsoft.Extensions.Hosting.Internal.ServiceFactoryAdapter`1.CreateServiceProvider(Object containerBuilder)
   at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at CareSwitch.Program.<Main>d__0.MoveNext() in C:\Users\MarkFayngersh\source\repos\CareSwitch Blazor\Program.cs:line 18

Inner Exception 1:
InvalidOperationException: Error while validating the service descriptor 'ServiceType: Microsoft.Extensions.Hosting.IHostApplicationLifetime Lifetime: Singleton ImplementationType: Microsoft.Extensions.Hosting.Internal.ApplicationLifetime': A circular dependency was detected for the service of type 'Microsoft.JSInterop.IJSRuntime'.
Microsoft.Extensions.Hosting.IHostApplicationLifetime(Microsoft.Extensions.Hosting.Internal.ApplicationLifetime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>) -> Microsoft.JSInterop.IJSRuntime(Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>) -> Microsoft.JSInterop.IJSRuntime

Inner Exception 2:
InvalidOperationException: A circular dependency was detected for the service of type 'Microsoft.JSInterop.IJSRuntime'.
Microsoft.Extensions.Hosting.IHostApplicationLifetime(Microsoft.Extensions.Hosting.Internal.ApplicationLifetime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>) -> Microsoft.JSInterop.IJSRuntime(Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>) -> Microsoft.JSInterop.IJSRuntime

Error goes away as soon as I remove the call to .AddBrowserConsole().

Versions

  • ASP.NET Core Blazor Server app - v3.0.0
  • Blazor.Extensions.Logging - v1.0.0

created time in 17 days

issue commentBlazorExtensions/Logging

Some services are not able to be constructed

It appears there is a circular dependency between IJSRuntime and BrowserConsoleLogger which may be at the core of this error.

The error I'm seeing:

System.AggregateException
  HResult=0x80131500
  Message=Some services are not able to be constructed
  Source=Microsoft.Extensions.DependencyInjection
  StackTrace:
   at Microsoft.Extensions.DependencyInjection.ServiceProvider..ctor(IEnumerable`1 serviceDescriptors, ServiceProviderOptions options)
   at Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider(IServiceCollection services, ServiceProviderOptions options)
   at Microsoft.Extensions.DependencyInjection.DefaultServiceProviderFactory.CreateServiceProvider(IServiceCollection containerBuilder)
   at Microsoft.Extensions.Hosting.Internal.ServiceFactoryAdapter`1.CreateServiceProvider(Object containerBuilder)
   at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at CareSwitch.Program.<Main>d__0.MoveNext() in C:\Users\MarkFayngersh\source\repos\CareSwitch Blazor\Program.cs:line 18

Inner Exception 1:
InvalidOperationException: Error while validating the service descriptor 'ServiceType: Microsoft.Extensions.Hosting.IHostApplicationLifetime Lifetime: Singleton ImplementationType: Microsoft.Extensions.Hosting.Internal.ApplicationLifetime': A circular dependency was detected for the service of type 'Microsoft.JSInterop.IJSRuntime'.
Microsoft.Extensions.Hosting.IHostApplicationLifetime(Microsoft.Extensions.Hosting.Internal.ApplicationLifetime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>) -> Microsoft.JSInterop.IJSRuntime(Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>) -> Microsoft.JSInterop.IJSRuntime

Inner Exception 2:
InvalidOperationException: A circular dependency was detected for the service of type 'Microsoft.JSInterop.IJSRuntime'.
Microsoft.Extensions.Hosting.IHostApplicationLifetime(Microsoft.Extensions.Hosting.Internal.ApplicationLifetime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.Extensions.Hosting.Internal.ApplicationLifetime>) -> Microsoft.JSInterop.IJSRuntime(Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime) -> Microsoft.Extensions.Logging.ILogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>(Blazor.Extensions.Logging.BrowserConsoleLogger<Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime>) -> Microsoft.JSInterop.IJSRuntime
moonolgerd

comment created time in 17 days

issue openedOmniSharp/omnisharp-vscode

VS Code Razor syntax highlighting and intellisense not working

Screenshot

Annotation 2019-10-30 130044

Versions

  • Visual Studio Code:
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

<details><summary>Mono Information</summary> OmniSharp using built-in mono</details> <details><summary>Dotnet Information</summary> .NET Core SDK (reflecting any global.json): Version: 3.0.100 Commit: 04339c3a26

Runtime Environment: OS Name: debian OS Version: 10 OS Platform: Linux RID: debian.10-x64 Base Path: /usr/share/dotnet/sdk/3.0.100/

Host (useful for support): Version: 3.0.0 Commit: 7d57652f33

.NET Core SDKs installed: 3.0.100 [/usr/share/dotnet/sdk]

.NET Core runtimes installed: Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download </details> <details><summary>Visual Studio Code Extensions</summary>

Extension Author Version
azure-account ms-vscode 0.8.6
azure-pipelines ms-azure-devops 1.157.4
csharp ms-vscode 1.21.5
docomment k--kato 0.1.8
rest-client humao 0.22.2
vscode-html-css ecmel 0.2.3
vscodeintellicode VisualStudioExptTeam 1.2.0

</details>

Additional Context

The app is being developed inside a container using Visual Studio Code Remote - Containers.

This same ASP.NET Core Blazor Server app works fine with proper Razor syntax highlighting and intellisense in Visual Studio 2019 v16.3.7

created time in 17 days

issue commentaspnet/AspNetCore

VS Code Razor syntax highlighting and intellisense not working

The app is being developed inside a container using Visual Studio Code Remote - Containers.

Additional environment info:

<details><summary>Mono Information</summary> OmniSharp using built-in mono</details> <details><summary>Dotnet Information</summary> .NET Core SDK (reflecting any global.json): Version: 3.0.100 Commit: 04339c3a26

Runtime Environment: OS Name: debian OS Version: 10 OS Platform: Linux RID: debian.10-x64 Base Path: /usr/share/dotnet/sdk/3.0.100/

Host (useful for support): Version: 3.0.0 Commit: 7d57652f33

.NET Core SDKs installed: 3.0.100 [/usr/share/dotnet/sdk]

.NET Core runtimes installed: Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download </details> <details><summary>Visual Studio Code Extensions</summary>

Extension Author Version
azure-account ms-vscode 0.8.6
azure-pipelines ms-azure-devops 1.157.4
csharp ms-vscode 1.21.5
docomment k--kato 0.1.8
rest-client humao 0.22.2
vscode-html-css ecmel 0.2.3
vscodeintellicode VisualStudioExptTeam 1.2.0

</details>

pheuter

comment created time in 17 days

issue openedaspnet/AspNetCore

VS Code Razor syntax highlighting and intellisense not working

Screenshot

Annotation 2019-10-30 130044

Versions

  • Visual Studio Code:
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362
  • ms-vscode.csharp extension - 1.21.5
  • ASP.NET Core using Blazor Server - 3.0.0

Additional Context

Same ASP.NET Core Blazor Server app works fine with proper Razor syntax highlighting and intellisense in Visual Studio 2019 v16.3.7

created time in 17 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

I can confirm it works now after I made the following changes:

Startup.cs

services.AddSignalR().AddAzureSignalR(options =>
{
    options.ServerStickyMode = Microsoft.Azure.SignalR.ServerStickyMode.Required;
});

Kubernetes Ingress definition

nginx.ingress.kubernetes.io/affinity: "cookie"
nginx.ingress.kubernetes.io/session-cookie-name: "affinity"
nginx.ingress.kubernetes.io/session-cookie-expires: "14400"
nginx.ingress.kubernetes.io/session-cookie-max-age: "14400"
pheuter

comment created time in 18 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

Thanks for the suggestion @javiercn, looks like you might be right. I'm going to give it a shot and report back,

Maybe this is just me not paying attention but the ASP.NET Core Blazor docs could probably make it clearer that there is additional setup involved to get sticky sessions working. The only documentation I found was this section that just talks about Azure App Service. And then this section talks about how when using Azure SignalR Service:

sticky sessions, also known as client affinity, is not required, because clients are immediately redirected to the Azure SignalR Service when they connect.

...which seems misleading.

pheuter

comment created time in 18 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

Not sure if it's related but I'm also loading Blazor.Polyfill before blazor.server.js for compatibility with IE11.

pheuter

comment created time in 18 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

Server-side logs:

dbug: Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher[1]
      Received hub invocation: InvocationMessage { InvocationId: "0", Target: "StartCircuit", Arguments: [ https://web.careswitch.com/, https://web.careswitch.com/login, [{"type":"server","sequence":0,"descriptor":"CfDJ8HBfOAK5iB9BiwSknWLLLPOeUDbgczl8pIbnhvcxj7QK-tKBIX3UjpzZAlAQd2-ptoPQswOOQHwosSy91nyi7NID_iAnuqy2FhG52glnEm-GyOj__AYIPz19MU188jpmofmGOgea2_uX8tGtzfVOUE0pNXvMpGfH6GY1Y312GW6Nl5px3MyFV7NACC6RxfNwmIB83og2_X-NSZLyUz7YGryKBcvHAId1mP2Ffg796OJ-6Hd7eLY7gPJsqpzT5oL8KxqJ5UN6LiH2zVBhKSUr88AKdBZzJta0VgSEDXEpENMe"}] ], StreamIds: [  ] }.

Client-side logs

[Error] Failed to load resource: the server responded with a status of 400 () (disconnect, line 0)
[Info] [2019-10-30T00:48:41.261Z] Information: Normalizing '_blazor' to 'https://web.careswitch.com/_blazor'. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.261Z] Debug: Starting HubConnection. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.262Z] Debug: Starting connection with transfer format 'Binary'. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.262Z] Debug: Sending negotiation request: https://web.careswitch.com/_blazor/negotiate. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.300Z] Debug: Sending negotiation request: https://careswitch-web.service.signalr.net/client/negotiate?hub=componenthub&asrs.op=%2F_blazor&asrs_request_id=O%2BVldtCqFAA%3D. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.341Z] Debug: Selecting transport 'WebSockets'. (blazor.server.js, line 1)
[Info] [2019-10-30T00:48:41.447Z] Information: WebSocket connected to wss://careswitch-web.service.signalr.net/client/?hub=componenthub&asrs.op=%2F_blazor&asrs_request_id=O%2BVldtCqFAA%3D&id=Kt0js0GFTRqcQVwzZDzoUgd58b758b1&access_token=eyJhbGciOiJIUzI1NiIsImtpZCI6IjA2a2tHUVkwVHg1K3hvZHR3TUd2T0F4MFpqZWJWMVBpdGNiTmdkL1ZXL1E9IiwidHlwIjoiSldUIn0.eyJhc3JzLnMuaWQiOiJvN1pqZHRDcUZBQT0iLCJuYmYiOjE1NzIzOTY1MjEsImV4cCI6MTU3MjQwMDEyMSwiaWF0IjoxNTcyMzk2NTIxLCJhdWQiOiJodHRwczovL2NhcmVzd2l0Y2gtd2ViLnNlcnZpY2Uuc2lnbmFsci5uZXQvY2xpZW50Lz9odWI9Y29tcG9uZW50aHViIn0.Q37VDB6ZclJVvrKD26l9NhebAdOBTNmOz-ipD0hhv3I. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.447Z] Debug: The HttpConnection connected successfully. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.448Z] Debug: Sending handshake request. (blazor.server.js, line 1)
[Info] [2019-10-30T00:48:41.448Z] Information: Using HubProtocol 'blazorpack'. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.529Z] Debug: Server handshake complete. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.529Z] Debug: HubConnection connected successfully. (blazor.server.js, line 1)
[Error] [2019-10-30T00:48:41.589Z] Error: The list of component records is not valid.
	(anonymous function) (blazor.server.js:15:27319)
	S (blazor.server.js:8:104321)
	(anonymous function) (blazor.server.js:8:103847)
	forEach
	(anonymous function) (blazor.server.js:1:19127)
	(anonymous function) (blazor.server.js:1:17184)
	(anonymous function) (blazor.server.js:1:38037)
[Log] [2019-10-30T00:48:41.589Z] Debug: Stopping HubConnection. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.590Z] Debug: HttpConnection.stopConnection(undefined) called while in state Disconnecting. (blazor.server.js, line 1)
[Info] [2019-10-30T00:48:41.590Z] Information: Connection disconnected. (blazor.server.js, line 1)
[Log] [2019-10-30T00:48:41.590Z] Debug: HubConnection.connectionClosed(undefined) called while in state Disconnecting. (blazor.server.js, line 1)
[Error] Unhandled Promise Rejection: Error: Invocation canceled due to the underlying connection being closed.
	(anonymous function) (blazor.server.js:8:100661)
	a (blazor.server.js:8:99498)
	promiseReactionJob

Possibly also worth noting that it works roughly a third of the time, which suggests that it doesn't like it when the WebSocket connection goes to a server other than the one that prerendered the initial view.

pheuter

comment created time in 18 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

@anurse I will setup the tracing shortly, just want to further clarify that everything works as expected when I simply change the Kubernetes deployment replica size to 1. This means that requests to that single pod are still routed through the same load balancer and nginx ingress controller, and the wss:// connection appears to work just fine.

pheuter

comment created time in 18 days

issue commentaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

Sure thing, @danroth27

3 servers is misleading. The actual environment is a Kubernetes deployment of replica size 3 on an AKS cluster, so it's really 3 pods potentially running across 3 VMs in a VNet managed by the AKS cluster. The load balancer is provisioned automatically on Azure using a Kubernetes Nginx ingress controller.

pheuter

comment created time in 18 days

issue openedaspnet/AspNetCore

ASP.NET Core 3.0 Blazor Server fails to load when deploying multiple servers

Versions

  • ASP.NET Core - v3.0.0
  • Microsoft.Azure.SignalR - v1.1.1 (deployed on Azure using Standard pricing and Default model)

Startup Configuration

services.AddSignalR().AddAzureSignalR();
services.AddRazorPages();
services.AddServerSideBlazor();

Error

In the browser console:

Error: The list of component records is not valid.
Uncaught (in promise) Error: Invocation canceled due to the underlying connection being closed.

Additional context

This error only occurs when I deploy the ASP.NET Core app to multiple servers behind a load balancer. The docs seem to suggest that when using Azure SignalR Service, sticky sessions are handled automatically for you, but this error appears to suggest otherwise?

created time in 18 days

created tagCareSwitch/docker-runtime

tag3.0.0_12.13.0

ASP.NET Core runtime image based on microsoft-dotnet-core-aspnet

created time in a month

release CareSwitch/docker-runtime

3.0.0_12.13.0

released time in a month

push eventCareSwitch/docker-runtime

Mark Fayngersh

commit sha 06ae54c75f99e455e51c35a8982f79a56d6aaf7e

3.0.0_12.13.0

view details

push time in a month

created tagCareSwitch/docker-sdk

tag3.0.100_12.13.0

.NET Core SDK image based on microsoft-dotnet-core-sdk. Used for dev.

created time in a month

release CareSwitch/docker-sdk

3.0.100_12.13.0

released time in a month

push eventCareSwitch/docker-sdk

Mark Fayngersh

commit sha 5f1b452aa07d7a21026aa747a2a899905db4e939

Update to dotnet v3.0 and node v12.13.0

view details

push time in a month

startedframer/motion

started time in a month

startedreact-hook-form/react-hook-form

started time in a month

startedmicrosoft/cascadia-code

started time in 2 months

startedmicrosoft/PowerToys

started time in 2 months

issue commentmicrosoft/vscode-react-native

Support for VS Code Remote Containers

@ruslan-bikkinin That's exactly right.

ruslan-bikkinin

comment created time in 3 months

issue commentmicrosoft/vscode-react-native

Support for VS Code Remote Containers

Sure, and feel free to correct me if I misunderstood the use case. From my perspective I see Remote Containers as the tool by which I can enforce a consistent development environment across platforms. By setting up a Docker image with all the necessary prerequisites, as well as controlling the version of Node, developers are then able to work on the codebase with tools like autocompletion and consistent local environments.

For this reason I don't see local development and debugging on a React Native project as any different than a Node / React project and assumed that it should work via Remote Containers just the same.

ruslan-bikkinin

comment created time in 3 months

more