I’m surprised that the self-contained option isn’t the default. One of the value props of .NET Core/.net 5 is that you can deploy without relying on any dependencies. When pushing to Azure Web App/Service I nearly always use the self-contained option – this gives me 100% control over which framework version I’m using.
Unfortunately you can’t always do this – for example because of the hosting model for Azure Functions you have to use a framework version that’s supported. This will change with the new hosting model (actually it’s basically the same hosting model that’s used for all other frameworks other than .NET) is introduced for .NET 5 support. Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Director | +61 412 413 425 | 1300 613 140 | www.builttoroam.com<https://www.builttoroam.com/> The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: [email protected] <[email protected]> On Behalf Of Greg Keogh Sent: Wednesday, 25 November 2020 9:14 AM To: ozDotNet <[email protected]> Subject: Re: Blazor server deploy to Azure Have you got the right version of for net core installed on the server? Since I'm deploying to an Azure Web App I thought that was out of my control -- GK
