After upgrading to respectively installing Visual Studio 2017 Version 15.6 no assemblies will be signed with a strong name.

We are using the AssemblyKeyName Attribute in AssemblyInfo.cs.

Using a KeyFile instead (created from the projects properties) will work.

Am I missing something?

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/209811/strong-name-signing-with-a-key-installed-in-a-cont.html
VSTS ticketId: 578075
These are the original issue comments:

Matthew Dodds on 3/7/2018, 10:24 AM (12 hours ago):

I am also having this problem with using AssemblyKeyName, which is showing up as two different issues. I am using C#, ASP.NET, .NET 4.7.1. Both of these issues were fixed once I reverted to Visual Studio 15.5.7. I also confirmed that using AssemblyKeyFile referencing a .snk instead of using AssemblyKeyName fixed both issues.

First:

Attempting to load the program in IIS results in the exception: "Could not load file or assembly '[redacted], Culture=neutral, PublicKeyToken=928c297f0d8e5e72' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference."

Fusion log contained: "Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN"

Second:

Building of a solution that references some of our C# libraries built outside of the solution will result in: "Error CS8002: Referenced assembly '[redacted], Version=6.3.0.144, Culture=neutral, PublicKeyToken=null' does not have a strong name."

Building this solution a second time will result it successfully building, but will always fail if telling Visual Studio to rebuild.

These are the original issue solutions:
(no solutions)