Gertjan's blog

For migrating an Azure Function app from .NET Core v2 to v3 follow the following steps Unload the Azure function project by right clicking the project and selecting unload. Change   <propertygroup>    <targetframework>netcoreapp2.2</targetframework>    <azurefunctionsversion>v2</azurefunctionsversion>   </propertygroup>           to   <propertygroup>     <targetframework>netcoreapp3.1</targetframework>     <azurefunctionsversion>v3</azurefunctionsversion>   </propertygroup> Reload the Azure function project by right clicking the unloaded project Update the Microsoft.NET.Sdk.Functions nuget package to version 3.0.2 or higher Update the Microsoft.Azure.WebJobs.Extensions (when installed) to version 4.0.0 or higher In the local.settings.json change the FUNCTIONS_EXTENSION_VERSION setting to "~3" ...

For migrating your .NET Core v2 MVC app to v3 use the following steps Change the .NET Core version of your web app to .NET Core v3.1 or higher Change your Startup.cs in your web root Remove the following line services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_2); Add the following line to the ConfigureServices method services.AddControllersWithViews(); Change the signature of method from public void Configure(IApplicationBuilder app, IHostingEnvironment env) to public void Configure(IApplicationBuilder app, IWebHostEnvironment env) If you use a env.IsDevelopment() statement add the following in the top of your Startup.cs using Microsoft.Extensions.Hosting; Add the following lines to the bottom of your Configure method app.UseRouting(); app.UseCors(); Only add the following lines if you use authentication / authorization app.UseAuthentication(); app.UseAuthorization(); Convert your web routes from app.UseMvc(routes => {        ...

After a windows update on a Windows server we got the following error messages when navigating to the reporting webservices or Reporting management website. These sites where protected bij SSL. Your TLS security settings aren't set to the defaults, which could also be causing this error. After a deep investigation we tried to change the TLS settings in the registry and configure the cipher algoritemes. Nothing worked. In the end we removed the SSL certificate from the Reporting Service Configuration manager. Then we we added the same certificate again to the Web Service Url and Report Manager Url. That fixed all.