2013.1.80.1 crash problem

Oystein Bjorke fa 10 anys 0
This discussion was imported from CodePlex

sunwayking wrote at 2013-09-07 10:46:

Oxyplot.WPF from Nuget crashes, one from CodePlex works well.
.Net Framewrok 4.5 x86 & x64
.Net Framewrok 4.0 x86 & x64
.Net Framewrok 4.0 Client Profile x86 & x64



发生了 System.Windows.Markup.XamlParseException
HResult=-2146233087
Message=未能加载文件或程序集“OxyPlot, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=638079a8f0bd61e9”或它的某一个依赖项。找到的程序集清单定义与程序集引用不匹配。 (异常来自 HRESULT:0x80131040)
Source=PresentationFramework
LineNumber=0
LinePosition=0
StackTrace:
   在 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
InnerException: System.IO.FileLoadException
   HResult=-2146234304
   Message=未能加载文件或程序集“OxyPlot, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=638079a8f0bd61e9”或它的某一个依赖项。找到的程序集清单定义与程序集引用不匹配。 (异常来自 HRESULT:0x80131040)
   Source=mscorlib
   FileName=OxyPlot, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=638079a8f0bd61e9
   FusionLog==== 预绑定状态信息 ===
日志: 用户 = VaeAnchoret\Vae Anchoret
日志: DisplayName = OxyPlot, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=638079a8f0bd61e9
(Fully-specified)
日志: Appbase = file:///C:/Users/Vae Anchoret/Desktop/Pipeline Security Pre-warning System_3进程版/Release/
日志: 初始 PrivatePath = NULL

调用程序集: OxyPlot.Wpf, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=75e952ba404cdbb0。

日志: 此绑定从 default 加载上下文开始。
日志: 正在使用应用程序配置文件: C:\Users\Vae Anchoret\Desktop\Pipeline Security Pre-warning System_3进程版\Release\ViewPluginTest.vshost.exe.Config
日志: 使用主机配置文件:
日志: 使用 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config 的计算机配置文件。
日志: 策略后引用: OxyPlot, Version=2013.1.80.1, Culture=neutral, PublicKeyToken=638079a8f0bd61e9
日志: 尝试下载新的 URL file:///C:/Users/Vae Anchoret/Desktop/Pipeline Security Pre-warning System_3进程版/Release/OxyPlot.DLL。
警告: 比较程序集名称时发生不匹配: 生成号
错误: 未能完成程序集的安装(hr = 0x80131040)。探测终止。
   StackTrace:
        在 System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
        在 System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
        在 System.Windows.Baml2006.Baml2006SchemaContext.ResolveBamlTypeToType(BamlType bamlType)
        在 System.Windows.Baml2006.Baml2006SchemaContext.ResolveBamlType(BamlType bamlType, Int16 typeId)
        在 System.Windows.Baml2006.Baml2006SchemaContext.GetXamlType(Int16 typeId)
        在 System.Windows.Baml2006.Baml2006Reader.Process_ElementStart()
        在 System.Windows.Baml2006.Baml2006Reader.Process_OneBamlRecord()
        在 System.Windows.Baml2006.Baml2006Reader.Process_BamlRecords()
        在 System.Windows.Baml2006.Baml2006Reader.Read()
        在 System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
        在 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   InnerException: 


objo wrote at 2013-09-11 23:31:

This seems to be fixed now!

sunwayking wrote at 2013-09-14 04:51:

objo wrote:
This seems to be fixed now!
That's great! I gonna have a try now.