This is a migrated thread and some comments may be shown as answers.

BindingFailure was Detected

1 Answer 104 Views

This is a migrated thread and some comments may be shown as answers.

Martin Sarosi asked on 25 Nov 2008, 04:14 PM

I have just upgraded to the latest controls.

2008.3.1105.20

Binding Failure MDA from the following code - a couple of times then it works ok. This only occurs in the IDE.

    
            RadMenu1.LoadXml(doc.SelectSingleNode(pathTo + "Menu").OuterXml); 
        
            TheToolbar.LoadXml(doc.SelectSingleNode(pathTo + "ToolBar").OuterXml);

There isn't a Telerik.Web.UI.XmlSerializers file
It seems to arise twice and then never again??

This is the result.
The assembly with display name 'Telerik.Web.UI.XmlSerializers' failed to load in the 'LoadFrom' binding context of the AppDomain with ID 2.
The cause of the failure was: System.IO.FileNotFoundException:
Could not load file or assembly 'Telerik.Web.UI.XmlSerializers, Version=2008.3.1105.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies.
The system cannot find the file specified.
File name: 'Telerik.Web.UI.XmlSerializers, Version=2008.3.1105.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4'

=== Pre-bind state information ===
LOG: User = ENGICA\Martin_Sarosi
LOG: DisplayName = Telerik.Web.UI.XmlSerializers, Version=2008.3.1105.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4, processorArchitecture=MSIL
(Fully-specified)
LOG: Appbase = file:///J:/MyApp/
LOG: Initial PrivatePath = J:\MyApp\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: J:\MyApp\web.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: Telerik.Web.UI.XmlSerializers, Version=2008.3.1105.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4, processorArchitecture=MSIL
LOG: The same bind was seen before, and was failed with hr = 0x80070002.

Cheers Marty

BindingFailure was Detected

1 Answer, 1 is accepted