Microsoft Update to Azure App Service broke our systems

Question

This update...

https://learn.microsoft.com/answers/questions/6842/announcement-samesite-cookie-handling-and-net-fram.html

...was rolled out to all our servers, dev, uat and our production Azure App Service all at once. It seems assemblies that we were deploying are now in the gac.

As a consequence we started encountering the following errors in code that uses RazorEngine to generate emails..

Error Details - Generated CS: Line: 0 Column: 0 Text: An assembly with the same identity 'Microsoft.Data.Edm, Version=5.8.4.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has already been imported. Try removing one of the duplicate references. Err#: CS1703
Error Details - Generated CS: Line: 0 Column: 0 Text: An assembly with the same identity 'Microsoft.Data.OData, Version=5.8.4.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has already been imported. Try removing one of the duplicate references. Err#: CS1703
Error Details - Generated CS: Line: 0 Column: 0 Text: An assembly with the same identity 'System.Spatial, Version=5.8.4.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has already been imported. Try removing one of the duplicate references. Err#: CS1703

RazorEngine.Templating.TemplateCompilationException: Unable to compile template. Check the Errors list for details.
at RazorEngine.Compilation.DirectCompilerServiceBase.CompileType(TypeContext context)
at RazorEngine.Templating.TemplateService.CreateTemplate(String template, Type modelType)
at RazorEngine.Templating.TemplateService.GetTemplate(String template, Type modelType, String name)
at RazorEngine.Templating.TemplateService.Compile(String template, Type modelType, String name)
at RazorEngine.Templating.TemplateService.CompileWithAnonymous(String template, String name)

Our fix for this issue was to change the references in our solution for these assemblies from "Copy Local = True" to "Copy Local = False".

These systems were functioning normally before we received notification this update had been applied to our Azure App Services. I'm almost betting this was a mistake and that when it's corrected we'll have another issue with these assemblies no longer being able to be loaded.

Microsoft should not be rolling out updates in this manner, like windows updates, Azure Developers should be able to roll out these updates to their servers in a controlled manner. If we had been able to do that we could have picked up these issues, determined a solution and scheduled some down time on our production systems to minimizing down time on our production systems, instead it's resulted in a large outage for our clients on Azure systems.

Answer 1

Hi @michael Lang this issue is not related to the same-site cookie rollout. However, the product group is aware of the issue and is the process of rolling out a fix to address it.