search

fsprojects / FsXaml

F# Tools for working with XAML Projects
http://fsprojects.github.io/FsXaml/
MIT License
172 stars 48 forks source link

v0.9.9 somehow tries to do something with v0.9.8 #17

Closed TeaDrivenDev closed 9 years ago

TeaDrivenDev commented 9 years ago

When using the current FsXaml version (both from the NuGet package as well as source-built assemblies) in a project, I get an error on the line

type App = FsXaml.XAML<"App.xaml">

saying

The type provider 'FsXaml.XamlTypeProvider' reported an error: Could not load type 'FsXaml.XamlResourceFactory' from assembly 'FsXaml.Wpf, Version 0.9.8.0, Culture=neutral, PublicKeyToken=null'.

I can't imagine how it would get the idea to look for 0.9.8 when both assemblies are 0.9.9. For lack of any better ideas, I have tried adding a binding redirect to 0.9.9, but to no avail.

All projects use the 4.5 runtime and F# 3.1. The demo project for FSharp.Desktop.UI in the FsXaml repository works fine.

Any ideas? Am I missing something?

ReedCopsey commented 9 years ago

Did you rebuild the main project? It uses reference from bin folder in fsproj files.

Sent from my iPhone

On Oct 11, 2014, at 5:52 PM, TeaDrivenDev notifications@github.com wrote:

When using the current FsXaml version (both from the NuGet package as well as source-built assemblies) in a project, I get an error on the line

type App = FsXaml.XAML<"App.xaml"> saying

The type provider 'FsXaml.XamlTypeProvider' reported an error: Could not load type 'FsXaml.XamlResourceFactory' from assembly 'FsXaml.Wpf, Version 0.9.8.0, Culture=neutral, PublicKeyToken=null'. I can't imagine how it would get the idea to look for 0.9.8 when both assemblies are 0.9.9. For lack of any better ideas, I have tried adding a binding redirect to 0.9.9, but to no avail.

All projects use the 4.5 runtime and F# 3.1. The demo project for FSharp.Desktop.UI in the FsXaml repository works fine.

Any ideas? Am I missing something?

— Reply to this email directly or view it on GitHub.

TeaDrivenDev commented 9 years ago

As it turns out, the issue was apparently caused by another Visual Studio instance that was open since before I installed the new package, still "knew" about the previous version and somehow prevented a proper update as far as VS itself was concerned. After closing all open VS instances and reopening my project, the error was gone.