SAFE-BookStore
SAFE-BookStore copied to clipboard
Working sample of a SAFE-Stack project with hot reloading
### A clean build of a fresh pull of safe-bookstore fails when it tries to reinstall the dotnetskd I did a fresh pull of the repo and a ./build.sh and...
### Description I was following steps provided on ReadMe for Azure. ### Repro steps Follow the steps on Read me for Azure other than Storage part. ### Expected behavior It...
In the manual validation that our vendors are doing, I had bad repro steps and didn't explicitly call out that Node and Yarn are requirements. This resulted in a manual...
> ERROR in C:/Users/kirichenko/.nuget/packages/fable.elmish.browser/1.0.0/fable/navigation.fs Module not found: Error: Can't resolve '../../../fable.core/1.2.4/fable-core/Option' in 'C:\Users\kirichenko\.nuget\packages\fable.elmish.browser\1.0.0\fable' @ C:/Users/kirichenko/.nuget/packages/fable.elmish.browser/1.0.0/fable/navigation.fs 8:0-71 @ ./App.fs @ ./Client.fsproj ERROR in C:/Users/kirichenko/.nuget/packages/fable.elmish.browser/1.0.0/fable/parser.fs Module not found: Error: Can't resolve '../../../fable.core/1.2.4/fable-core/Option'...
### Description Compiler errors in VS code but site still works and editor changes are reflected. ### Repro steps 1. Install prerequisites. 2. Clone repo 3. Run ``build.cmd`` 4. Open...
``` Restore completed in 15,71 ms for D:\WLCR\github\SAFE-BookStore\src\Client\Client.fsproj. D:\WLCR\github\SAFE-BookStore\src\Client\Client.fsproj : warning NU1603: Fable.Compiler 1.2.4 depends on FSharp.Compiler.Service (>= 14.0.2) but FSharp.Compiler.Service 14.0.2 was not found. An approximate best match of...
It is more of a question then an issue. So, feel free to close it. And I m docker noob, so don't mind my queries. Didn't find better place to...
### Description An alternative (and probably more well-known) mechanism to deploy .NET applications on the Azure App Service is through Kudu without the dependency on Docker and ACS. There should...
Currently we run the integration tests against the "dotnet run" version of the server. This is fine for fast test. But in release process we should start up the container...