Don Syme
Don Syme
The message is definitely useful to have at a fairly high log level. I'm just wondering if there is some way to disable it for the "let thespian" binding in...
Basically, to summarise: I don't know how to do rapid iterative development for a collection of Paketized projects publishing nuget components
@forki @isaacabraham I took a look at what this would mean in practice for these projects. It works OK when you have "Project2 --> Project1" dependencies. But it really doesn't...
Very simple diamond like this:: StarterKit --> MBrace.Azure --> MBrace.Core StarterKit --> MBrace.AWS --> MBrace.Core
@Krzysztof-Cieslak Yes, I figured it would hit that
@isaacabraham I am wondering if it is a mistake to have Thespian, Vagabond, MBrace.Core, MBrace.Azure, MBrace.AWS and MBrace.StarterKit all in separate projects, and all available as separate public nuget packages....
> if we were to push all those five or six packages into one, wouldn't that greatly increase the size of the client download (as well as make updates much...
@MaxWilson Yes, unfortunately this means the tutorial is no longer valid, and there is no simple getting-started path for MBrace at the moment. We will need to adjust the docs...
I'm watching from a distance and plan to get back to being more involved :)
@isaacabraham IIRC this is a tricky issue. The version of FSharp.Core on the worker nodes needs to match the version of FSharp.Core in the client FSI.EXE This really means we...