Answered by:
Help!? - Assembly bindings...

-
Hi there,
pulling my hair out for too long on this... perhaps I'm too close to it... can anyone help?
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Running under executable C:\Program Files (x86)\IIS Express\iisexpress.exe --- A detailed error log follows. === Pre-bind state information === LOG: DisplayName = Microsoft.Practices.EnterpriseLibrary.Logging, Version=6.0.1304.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (Fully-specified) LOG: Appbase = file:///D:/dev/src/webservice/ LOG: Initial PrivatePath = D:\dev\src\webservice\bin Calling assembly : (Unknown). === LOG: This bind starts in default load context. LOG: Using application configuration file: D:\dev\src\webservice\web.config LOG: Using host configuration file: \\cserver\users$\nojedi\IISExpress\config\aspnet.config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config. LOG: Post-policy reference: Microsoft.Practices.EnterpriseLibrary.Logging, Version=6.0.1304.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/Temporary ASP.NET Files/vs/d873c2ef/6d1debef/Microsoft.Practices.EnterpriseLibrary.Logging.DLL. LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/Temporary ASP.NET Files/vs/d873c2ef/6d1debef/Microsoft.Practices.EnterpriseLibrary.Logging/Microsoft.Practices.EnterpriseLibrary.Logging.DLL. LOG: Attempting download of new URL file:///D:/dev/src/webservice/bin/Microsoft.Practices.EnterpriseLibrary.Logging.DLL. WRN: Comparing the assembly name resulted in the mismatch: Build Number ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
this is in web.config
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Practices.ServiceLocation" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Practices.EnterpriseLibrary.Logging" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.1304.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Practices.EnterpriseLibrary.Common" publicKeyToken="31bf3856ad364e35" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.1304.0" /> </dependentAssembly> </assemblyBinding> </runtime>
tried removing the EntLib entries
tried changeing the "new version" to 6.0.0.0
file
D:/dev/src/webservice/bin/Microsoft.Practices.EnterpriseLibrary.Logging.DLL
IS 6.0.1304.0 (according to filemanager/winexplorer)
can anyone help please?!
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -
Question
Answers
-
hi dan, thanks for the heads up... but its sad really because its got almost nothing specifically to do with ASP/web, specifically as the web.config could just as easily been an app.config file (yes I'm building a webservice but its an fusion/assembly issue which I tried out in a console and got the same results)... maybe its an issue with .net/entlib 6/visual studio/nuget perhaps? (guess because when you add packages in VS it adds the assembly binding entries for you (which you can disable, I discovered.... maybe I should do that...?!)
anyway I solve it just now, not really sure why but it wanted:
6.0.1304.0 to be included in the "old" version... then it worked fine... odd, but okay at least I figured it out.
liek this:
<bindingRedirect oldVersion="0.0.0.0-6.0.1304.0" newVersion="6.0.1304.0" />
Go figure...
anyway maybe this will help someone oneday... :)
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -
- Marked as answer by noJedi Wednesday, May 04, 2016 4:49 PM
All replies
-
No one will answer this question here because you need to use asp.net for your web development questions.
Dan Randolph - My Code Samples List
-
hi dan, thanks for the heads up... but its sad really because its got almost nothing specifically to do with ASP/web, specifically as the web.config could just as easily been an app.config file (yes I'm building a webservice but its an fusion/assembly issue which I tried out in a console and got the same results)... maybe its an issue with .net/entlib 6/visual studio/nuget perhaps? (guess because when you add packages in VS it adds the assembly binding entries for you (which you can disable, I discovered.... maybe I should do that...?!)
anyway I solve it just now, not really sure why but it wanted:
6.0.1304.0 to be included in the "old" version... then it worked fine... odd, but okay at least I figured it out.
liek this:
<bindingRedirect oldVersion="0.0.0.0-6.0.1304.0" newVersion="6.0.1304.0" />
Go figure...
anyway maybe this will help someone oneday... :)
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -
- Marked as answer by noJedi Wednesday, May 04, 2016 4:49 PM