Richard Harding
Richard Harding
So I think Ionide is not relevant here? - should just run at cmd line with dotnet build I think?
not using Visual Studio - vs code with Ionide - have followed the guidance at Microsoft/visualfsharp#3303 ie by adding the fsc.props project import but still get that error
I was still getting the same issue - I created a new console app 2.1.403 sdk and now I get an error when paket attempts to install the package ```...
using the fsc.props workaround - have other type providers working fine with that, not using visual studio - just vscode, dotnet cmd line
no problem it was just something I needed for a project - do you have an idea when this will be supported in the published npm?
struggling to see how to do this in a non breaking way - thought I could re-define the builder to use ```#DurableOrchestrationContextBase``` which compiles but the ```orchestration``` ce still expects...
yeah that was my first attempt and that works but that means function definitions such as this break ``` [] let Run ([] context: DurableOrchestrationContext) = context |> orchestrator {...
this would be really useful to have
Have just hit this when trying to use Foq to mock the ```Microsoft.Azure.WebjobsDurableOrchestrationContextBase``` type - I was attempting port the sample here https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-unit-testing#unit-testing-orchestrator-functions to use Foq It should be noted...
So Am I better off building a console app exe than using fsx which generates a new one for the same file each time its run?