Unpin assembly version

[TylerLeonhardt]

Looks like the assembly version is out of sync with the actual version.

This causes issues when loading from the GAC on .NET Framework because if v3 of Serilog.Sinks.File is loaded in the GAC with assembly version 2.0.0.0... and we depend on Serilog.Sinks.File v4 functionality... things won't work.

As seen here: PowerShell/vscode-powershell#2538

[rjmholt]

See PowerShell/vscode-powershell#2538 (comment) and PowerShell/vscode-powershell#2538 (comment) for the particular breakdown of the issue.

I see in serilog/serilog#1319 that this is by design. Is there a way to ensure we load the right DLL?

[nblumhardt]

Probably time to unpin, now that the NuGet/.NET ecosystem has settled down a bit around this 👍

[dkattan]

What are the next steps here?

What's the worst that can happen if we unpin the version?

[nblumhardt]

@dkattan let's find out! :-)

(Most likely - we'll see an uptick in support requests from folks whose tooling doesn't generate binding redirects correctly, which was a major pain in the past, but should hopefully be less so now.)