Claire Novotny

@jskeet if you hover over the red/yellow icons, it'll tell you what the problem is in a tooltip. I agree there should be a better way to expose this.

Can we verify fixed in the latest (which uses 60011), based on later nuget code?

@Bhaal22 not sure what you mean by the cast not being possible?

The PR has some issues, AFAIK. Happy to review it if someone else wants to jump in.

It's possible there's a bug in the chocolatey version; it should store the MRU in the local settings: The store version remembers these for me: 

> Maybe we should also set a the NuGetPackageExplorer to get a nicer settings folder name? But maybe that will lose the existing settings... Probably....and/or it can be addressed by...

As a workaround for NuGet, and better than snupkg IMO, is to include the PDB in the main NuPkg. You can do that like this: https://github.com/clairernovotny/DeterministicBuilds/blob/master/Directory.Build.props#L10

@sakno that works too

Where would you expect to see this? I'm not sure it would go under package health as strong naming isn't a hard requirement anywhere (and is ignored on all platforms...

@campersau we could add an analysis to see if all assemblies in `ref`, `lib` and `runtimes` directories are strong named, though I tend to assume that it'd be rare for...