Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > ORM Profiler Section > Bugs & Issues> Exception with SD.Tools.BCLExtensions V1.1
 

Pages: 1
Bugs & Issues
Exception with SD.Tools.BCLExtensions V1.1
Page:1/1 

  Print all messages in this thread  
Poster Message
Jeremy Thomas
User



Location:
Wellington, New Zealand
Joined on:
29-Aug-2011 01:25:12
Posted:
36 posts
# Posted on: 11-Aug-2016 12:09:04.  
I have a Web App which uses SD.Tools.BCLExtensions.
I recently updated it to V1.1 but now if the ORM Profiler is enabled I get this;
Code:
An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/1/ROOT/AQDPortal.MVC.V8Dev

Process ID: 16624

Exception: System.IO.FileLoadException

Message: Could not load file or assembly 'SD.Tools.BCLExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a3f87088dcb994e1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

StackTrace:    at SD.Tools.OrmProfiler.Shared.CallStack.GetObjectData(SerializationInfo info, StreamingContext context)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at SD.Tools.OrmProfiler.Shared.MessageSerializers.SerializeMessage(IMessage message)
at SD.Tools.OrmProfiler.Interceptor.Channels.NamedPipeChannel.GetMessagesToSend()
at SD.Tools.OrmProfiler.Interceptor.Channels.NamedPipeChannel.SendMessageToPipeThreadBody()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

I eventually fixed it by adding this to the web.config assemblyBinding
Code:
     <dependentAssembly>
        <assemblyIdentity name="SD.Tools.BCLExtensions" publicKeyToken="a3f87088dcb994e1" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.1.0.0" newVersion="1.1.0.0" />
     </dependentAssembly>

Is this what you would expect?
Jeremy Thomas  Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
612 posts
# Posted on: 12-Aug-2016 09:25:22.  
the interceptor uses also bclextensions and that's v1.0. So as the app you're profiling uses 1.1, it couldn't load 1.0 and gave this exception. The assembly redirect is then a good solution.

Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.09082011 Final.