On November 8, 2022, Microsoft released .Net 7. After getting Visual Studio Professional 17.4 installed, updating to .Net 7 was fairly painless.
Changing the obligatory TargetFramework entry in all the projects:
Updating the package references from 6.0.0 to 7.0.0:
<PackageReference Include="Microsoft.Extensions.Hosting" Version="7.0.0" />
Updating the github action yml file to use the new dotnet version:
Azure even had all the website hosting ready so I didn't have to wait for anyone to deploy .Net 7. Microsoft does list some incompatabilities in .Net 7, but it's not a long list. This has probably been the easiest migration since .net46 to .net48.
Microsoft has a very large quantity of documentation on Azure. But most of those articles are focused on new large scale production scenarios, or migrating existing production scenarios to Azure. For a software development firm that is looking only to leverage Azure for software development and testing, and not expose public web services to the internet, where does one start?
The Micorosft documentation that I've read leads one to believe that it's a simple as just creating an Azure VM or an Azure Web service and your done. The reality is there is much more infrastructure required to do that. This series attempts to put together a roadmap or summary of some solutions aimed solely toward software development for Enterprise services and applications. You may find it helpful for preparing your Azure migration or if you have some services in Azure extending it.More...