The packages only used in the tutorials are still fectched during the sln build. I changed this recently, by manually adding the FSharpCharting nuget dependency to packages.config [here](https://github.com/fsharp/FSharp.Data/blob/9c3dc48f32d42bba752b91b9bf6c5550d8c5a9b2/tests/FSharp.Data.Tests.Documentation/packages.config#L3), and then I removed the package restore from build.fsx [here](https://github.com/fsharp/FSharp.Data/commit/67737ee76c6c187b4a41b2bda4e9228a83b8ba15)

I would like that when someone downloads or clones the source code to be able to get by just by opening the .sln and building inside VS and trying out the samples, not having to do any `./configure`, or `build.fsx` before. In my view, fake scripts should only be used to extra stuff like generating documentation and automating the releases. 
@forki Maybe you just built the main solution and open the samples directly instead of from the tests .sln? In that case maybe we should move the FSharp.Charting nuget reference to the packages.config of FSharp.Data.fsproj instead. Unfortunately, because of the type providers lock problem, we can't have the sample in the main solution, which would be ideal