The demos do not come with FsXaml.Wpf, FsXaml.Wpf.Blend and Fsharp.ViewModule.Core installed

[mrakgr]

As the title says. As a newbie to this, it was not immediately obvious what those 50 build errors meant. I had to compare it with the F# WPF template to figure out what is wrong. In addition to that the FSharpDesktopUINumericUpDown demo needs Fsharp.Desktop.UI as well. It might be good to have the necessary packages be automatically downloaded.

The FsXaml project in general needs some documentation for it.

[ReedCopsey]

it uses paket, so you need to run paket install from a command prompt.
I'll try to add some build instructions.

On Jul 15, 2016 9:17 AM, "mrakgr" notifications@github.com wrote:

As the title says. As a newbie to this, it was not immediately obvious
what those 50 build errors meant. I had to compare it with the F# WPF
template to figure out what is wrong. In addition to that the
FSharpDesktopUINumericUpDown demo needs Fsharp.Desktop.UI as well. It
might be good to have the necessary packages be automatically downloaded.

The FsXaml project in general needs some documentation for it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#43, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCUmvnxI_cGIaMxXUDJ6a5TNETH3pFlks5qV7J2gaJpZM4JNj8o
.

[JohanLarsson]

An alternative is to use paket.exe auto-restore on that way paket restores on build.

[JohanLarsson]

When thinking about this more I don't think the question is about paket at all.
Is there a reason the demo projects cannot be in the main sln? A sln folder /demos would simplify build and debugging.

[ReedCopsey]

@JohanLarsson Can't be in main project because of the type provider. If you do that, rebuilding the type provider requires shutting down VS entirely and restarting it.