Updated to FsXaml 0.9.9

[ReedCopsey]

Adjusted for new API changes in FsXaml.

[dungpa]

What does 'true' mean in this context? Could you add the argument name so that the purpose is clear?

[ReedCopsey]

Done. It exposes the named properties in the XAML file as properties on the RenameDialog type.

[dungpa]

Don't know why but I got this error when trying to open a dialog:

[ReedCopsey]

Which dialog? It sounds like, for some reason, you've got mixed assembly
versions (ie: an old FsXaml core library but a new type provider, or
something), but I'd like to make sure it wasn't a problem on my end.

On Thu, Oct 30, 2014 at 3:40 PM, Anh-Dung Phan [email protected]
wrote:

Don't know why but I got this error when trying to open a dialog:

[image: image]
https://cloud.githubusercontent.com/assets/941060/4853415/a1c6756a-6085-11e4-9f56-8b8cb4ab8222.png

—
Reply to this email directly or view it on GitHub
#808 (comment)
.

[dungpa]

I've got that error on all three dialogs.

Just double check versions of FsXaml.Wpf and FsXaml.Wpf.TypeProvider. They're both in 0.9.9.

[ReedCopsey]

@dungpa I can't duplicate - I just did a full rebuild, and installed the release version, in case it was a debug/release issue - working perfectly here. Debugging worked for me to change and test, too. The only way that message makes sense is if it's loading 0.9.8 or earlier of the core library (FsXaml.Wpf) somehow. Any ideas of what might be different? I'm in VS 2013. (Just trying to think of anything different at all...)

[ReedCopsey]

@dungpa I did notice that Paket is adding the references with Specific Version = false...not sure if that's having an impact /cc @forki

[dungpa]

I ran F5 from the Debug configuration.

It's the issue with type provider caches. I have to uncheck all the cache items and recheck the exact location (it has changed several times due to Paket) and rebuild everything. Now it works fine. Sorry for the false alert.