IIS deploy of a blazor InteractiveAuto application

[developer-sintmaartencampus]

Description

[Enter feedback here]
Since .Net 8 you can create a combination of a Blazer server and a blazer wasm application. I can find information how tho deploy either on of those, but not about a combined application.

Please advise.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-8.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/host-and-deploy/index.md

Document ID

c82cf121-831d-75dd-a796-c735aad3b3e9

Article author

@guardrex

[github-actions]

😎 Welcome April! Summertime is almost here! 🌞

A green dinosaur 🦖 will be along shortly to assist. Stand-by ........

[guardrex]

Hello @developer-sintmaartencampus ... It's this article ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server?view=aspnetcore-8.0

I think the ToC could use an update because it says "Blazor Server" in the node. I think it should probably read "Server-side" at this point to cover both Blazor Server and Blazor Web Apps.

I'll also probably change the introduction of that article to clearly call out that it applies to Blazor Server (still supported BTW) and Blazor Web Apps.

Thanks for the issue.

Leave this issue open, as it will close automatically when the PR merges.

[developer-sintmaartencampus]

There's literally just these 4 lines for IIS (including title) ;-)

IIS
When using IIS, enable:

WebSockets on IIS.
Sticky sessions with Application Request Routing.

When I publish my application, I find files in the release folder of both the Server as the Wasm-project. I need to publish on a subdomain, like staging.mywebapplication.com, I haven't figured out where I need to place the release-files of the Wasm-application.

I guess I do the sticky sessions (I've done Websockets), follow than the guidelines for path's 'n' stuff for the subdomain, and subsequently the rest of Blazor Server deployment.

Thank you for the swift reply. Sometimes knowing what you're looking for isn't there yet in abundance, is also a great help. I'm already less confused.

Take care and good luck.

[guardrex]

There's nothing more specific than this coverage and what appears at ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-8.0&source=recommendations&tabs=visual-studio#iis

The content of the publish folder should have the correct folder/file layout.

Everything else defaults back to our main doc set coverage because these are just server-side ASP.NET Core apps.

Things can get a little tricky with app base path changes for subapp hosting, and I hope if you're deploying that way that the app base path guidance in the overview Host and Deploy article help you get the configuration correct.

[guardrex]

BTW... ignore the release build folder in the client app AFAIK. I'll double check when I get back to the PC (I'm OOF at the moment), but you should be able to deploy only the publish assets from the main project. I'll add guidance on that when I work this issue.

The path of the published assets to deploy should be (unless the 🧀 has moved since then) ...

bin/Release/{TARGET FRAMEWORK}/publish

[guardrex]

Confirmed, @developer-sintmaartencampus! ... The publish folder location is ...

bin\Release\net8.0\publish\

... for an 8.0 BWA. Deploy from that folder only, and you should be alright.

I still have an update (or three! 😄) to make based on your issue. Leave this issue open, as it will close automatically when the PR merges. I hope to reach this for work next week.

[developer-sintmaartencampus]

Actually things have become really complicated with arr.

Here's my starting point.
A very simple webapplication for an organisation with a limited number a users. Some interactivity is required from the webapp. With a single server in the public network, that hosts the db, the website, the application.
(Some limited experience with running/co-managing a .Net/angular-app and a .Net Framework MVC app. And every time the server that hosted the webapp did also host the db and the website.) Also that blazor interactive feature looks cool ... .

The ARR comes a little bit as a surprise. In theory I could maintain just one server in the network, who exposes the IP/runs the website, but he also needs to steer the app servers and the db.

Where do I put my generated code? How do the application servers know what to do? I guess the DB Manager of IIS makes the link with the db for the whole farm.

https://learn.microsoft.com/en-us/iis/web-hosting/configuring-servers-in-the-windows-web-platform/application-request-routing-arr-20-for-shared-hosting?source=recommendations
https://learn.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/define-and-configure-an-application-request-routing-server-farm

[guardrex]

The best set of cross-links to guidance for your scenario with web farms is in the Publish an ASP.NET Core app to IIS article, which includes information on configuration of data protection. Combine that with the content behind the two cross-links provided in the server-side Host and deploy article (incorrectly named "Blazor Server" right now in the sidebar table of contents, which I'll update soon), you also should follow the cross-linked guidance in ...

• WebSockets on IIS
• Sticky sessions on IIS

I don't have further information other than the cross-links that I've provided. If you reach out to devs on public support forums, I'm certain that you'll find some folks who actively maintain web farms with Blazor apps. We recommend the usual places ...

• Stack Overflow (tag: blazor)
• ASP.NET Core Slack Team
• Blazor Gitter