-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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
Comments
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? |
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. |
UPDATE (7/6): Two aspects are being dropped from Blazor at 8.0, which result in closing this issue ...
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 ...
|
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.
The text was updated successfully, but these errors were encountered: