J
JrNona
Guest
Hi,
I'm running VS 2015 Version 14.0.25431.01 Update 3 with .Net Framework 4.7.03056.
Last week on Thursday I compiled my source code for a release and everything worked fine. Our network pushed out a KACE updated and on Friday morning when I came in and did a compile, my code failed. 1st it said that log4net was not found. So I reloaded that from NuGet. I attempted to compile again and I got a message that "Could not load file or assembly System.Net.Http.Formatting version: 5.2.7 When I look at the properties of my dll in Solution Explorer they are Runtime Version of v4.0.30319 and Version 5.2.3.0. I removed from Web.Config the following
<dependentAssembly>
<assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0" />
</dependentAssembly>
I did this for some other Asstemblies as well. Then the compile still failed.
Can anyone explain what is happening? I did a pull of a previous code version and the same errors occur.
Thanks
Bob
Continue reading...
I'm running VS 2015 Version 14.0.25431.01 Update 3 with .Net Framework 4.7.03056.
Last week on Thursday I compiled my source code for a release and everything worked fine. Our network pushed out a KACE updated and on Friday morning when I came in and did a compile, my code failed. 1st it said that log4net was not found. So I reloaded that from NuGet. I attempted to compile again and I got a message that "Could not load file or assembly System.Net.Http.Formatting version: 5.2.7 When I look at the properties of my dll in Solution Explorer they are Runtime Version of v4.0.30319 and Version 5.2.3.0. I removed from Web.Config the following
<dependentAssembly>
<assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.7.0" />
</dependentAssembly>
I did this for some other Asstemblies as well. Then the compile still failed.
Can anyone explain what is happening? I did a pull of a previous code version and the same errors occur.
Thanks
Bob
Continue reading...