Blazor Preview4 increase buffer size

Using the new Blazor Serverside Preview 4 breaks my upload Component.

Preview 3 I was able to increase the SignalR connection buffer size using

` app.UseRouting(routes =>
        {
            routes.MapRazorPages();
            routes.MapHub<ComponentHub>(
                ComponentHub.DefaultPath,
                o =>
                {
                    o.ApplicationMaxBufferSize = 102400000; // larger size
                    o.TransportMaxBufferSize = 102400000; // larger size
                })
                .AddComponent<App>("app");
        });`

In preview 4 it has switched to endpoint routing

app.UseEndpoints(endpoints =>
           {
               endpoints.MapBlazorHub();
               endpoints.MapFallbackToPage("/_Host");
           });

How would I configure MapBlazorHub(); Related Issue #7884

[julienGrd]

[EDIT] : I find the solution for preview 7 in another post, i put the solution bellow

pServices.AddServerSideBlazor()
            .AddHubOptions(o =>
             {
                 o.MaximumReceiveMessageSize = 102400000;
             });

Hi guys, i’m currently under preview 7 (server-side version) and i meet the same problem. i try to send a base64 string wich represent an image from js to one of my components (with JSInvokable). I try tu use code you suggest on this post but I have reference problem (maybe this workaround is outdated ?)

endpoints.MapBlazorHub<ComponentHub>(
                    ComponentHub.DefaultPath,
                    o =>
                    {
                        o.ApplicationMaxBufferSize = 102400000; // larger size
                        o.TransportMaxBufferSize = 102400000; // larger size
                    });

I’m unable to resolve ComponentHub. When i check what’s expected, it’s seem to be a IComponent (so my root Component ?)

I don’t understand what can i done now to bypass the problem

thanks for your help !

[tmayonez]

I’ve got the same problem. I’ve investigated that it’s not because MaximumReceiveMessageSize. It is impossible to invoke .NET method from javascript if parameters passed to method are to big. I guess, the limit of parameters serialized to JSON during invokeMethodAsync is 4KB. Worked fine before preview 4.