Open SergeyKanzhelev opened 5 years ago
The issue is caused by a broken template in Visual Studio that adds a DiagnosticSource binding redirect in web.config, but doesn’t publish the assembly.
web.config
<dependentAssembly> <assemblyIdentity name="System.Diagnostics.DiagnosticSource" publicKeyToken="cc7b13ffcd2ddd51" /> <bindingRedirect oldVersion="0.0.0.0-4.0.2.1" newVersion="4.0.2.1" /> </dependentAssembly>
Workaround if to remove that dependentAssembly node. VS folks are aware of the problem and they have a fix for it in 15.9.1
dependentAssembly
We may need to fix it by not crash if DiagnosticsSource cannot be found.
The issue is caused by a broken template in Visual Studio that adds a DiagnosticSource binding redirect in
web.config
, but doesn’t publish the assembly.Workaround if to remove that
dependentAssembly
node. VS folks are aware of the problem and they have a fix for it in 15.9.1We may need to fix it by not crash if DiagnosticsSource cannot be found.