SN issues with current System.Diagnostics.DiagnosticSource

[benaadams]

System.IO.FileLoadException : Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
---- System.Security.SecurityException : Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Stack Trace:
at Microsoft.AspNet.Hosting.WebApplicationBuilder.BuildHostingServices()
at Microsoft.AspNet.Hosting.WebApplicationBuilder.Build()
I:\Work\GitHub\KestrelHttpServer\test\Microsoft.AspNet.Server.Kestrel.FunctionalTests\PathBaseTests.cs(97,0): at Microsoft.AspNet.Server.Kestrel.FunctionalTests.PathBaseTests.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

[pranavkm]

This will get fixed in tomorrow's build of CoreCLR. For now, you might want to consider using sn -Vr to turn off strong name verification for this assembly. System.Text.Encodings.Web has a similar issue.

[benaadams]

This is resolved now.

[jruckert]

Same issue again

[benaadams]

Yep; CI is failing again

[Eilon]

I think this should now be fixed again... We added more checks for this prior to publishing so hopefully this doesn't return...

[davidfowl]

That has nothing to do with this issue, please open a new issue on ASP.NET home

[kscott5]

Yes, your correct. The image listed the version numbers only which was a bit misleading. I took it as if the assembly version was the CLR/Core CLR version.

Could you explain why now Main as entry point for execution?

I will open something on home if I can't resolve this issue.

Sent from my T-Mobile 4G LTE Device

-------- Original message --------
From: David Fowler
Date:01/19/2016 3:37 PM (GMT-06:00)
To: aspnet/Home
Cc: Karega Scott
Subject: Re: [Home] SN issues with current System.Diagnostics.DiagnosticSource (#1207)

That has nothing to do with this issue, please open something on ASP.NET home.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1207#issuecomment-172994820.