Skip to content

Deployment details to IIS are missing #28189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
GerardFR opened this issue Jan 25, 2023 · 3 comments
Closed

Deployment details to IIS are missing #28189

GerardFR opened this issue Jan 25, 2023 · 3 comments
Assignees
Labels
Blazor doc-enhancement Pri3 Source - Docs.ms Docs Customer feedback via GitHub Issue

Comments

@GerardFR
Copy link

This page gives many details on how to deploy an app to Azure, but it doesn't explain how to publish to an IIS server.
It would be great to add a section on that topic.


Document Details

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

@dotnet-bot dotnet-bot added Blazor Source - Docs.ms Docs Customer feedback via GitHub Issue labels Jan 25, 2023
@guardrex
Copy link
Collaborator

guardrex commented Jan 25, 2023

Thanks for the request, @GerardFR. True, devs at this time would piece it together from IIS and Windows cert management docs. It should be a bit easier to work out than the Azure case, which is why we've only been carrying Azure coverage. Devs were particularly tripped up by the exact Azure config to make it work.

@mkArtakMSFT ... This is a reasonable request. Devs unfamiliar with configuring the custom domain with the certificate for Identity Server's token signing key would benefit from a 🦖 Rex Mini-tutorial section™ 🦖. It would speed up the dev experience considerably over piecing it together from other docs. Shall I proceed to get this scheduled?

@guardrex
Copy link
Collaborator

guardrex commented Jan 30, 2023

I'll go ahead and schedule this. I think it's a good idea. Docs for this exist indirectly in two other doc sets, but I can whip up a section that will make it quick and easy for readers to implement.

UPDATE (5/15): I have taken a look at this, but it's a bit of a can of worms on the dB side. I don't have an IIS installation here, so I'd need to spin one up in Azure. Trying to configure and use a Win11 local IIS instance and SSMS wasn't fruitful. Malwarebytes is so opposed to it that they block IIS installation without notice. Disabling it allows installation, and apps run. However, there might be some SSMS installation problems (or post-installation configuration problems) because dB connections fail with ordinary connection strings. I wasn't able to quickly work out the reason for the failure. We'll take a look at this issue again later. Next time, I'll work it with an Azure VM for hopefully a better outcome.

@guardrex guardrex added the Pri3 label Jan 30, 2023
@guardrex
Copy link
Collaborator

guardrex commented Jul 6, 2023

UPDATE (7/6): Two aspects are being dropped from Blazor at 8.0, which result in closing this issue ...

  • First, the product unit has decided not to tie Blazor so tightly to IdS/Duende going forward, so they're dropping it from the project templates -- AND -- we won't be hosting specific guidance for IdS/Duende going forward >=8.0. The external (non-MS) doc sets for IdS/Duende and other IdPs offer their own project templates and guidance. Devs should look to those organizations to carry guidance on their products and features. For more information, see Auth improvements in ASP.NET Core 8 aspnetcore#47286 and Remove Duende from SPA and Blazor WASM project templates aspnetcore#47226.
  • Second ... and more importantly, the entire hosted WASM hosting option is being dropped from the framework. Devs will be encouraged to use the new Blazor Web App template and new auth API and features that they're rolling out for >=8.0. We'll cover new auth API and features for Blazor Web Apps and standalone (static) Blazor WebAssembly apps, including whatever we need for IIS, but we won't maintain or write new IIS coverage for hosted WebAssembly for >=8.0 articles.

For these reasons, we won't be addressing this issue. Most of the <8.0 guidance for hosted WASM with IdS for Azure is the same as it is for IIS. The same considerations must be taken into account, and the current release (7.0) Azure guidance is a good general approach for developing this type of app for IIS hosting. If anyone runs into trouble 😈, we recommend community support. Everyone is probably aware of the following forums and resources that we recommend ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blazor doc-enhancement Pri3 Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
Archived in project
Development

No branches or pull requests

3 participants