Enrico Sada

the `microsoft/dotnet` container is .net core (linux container) + .net (win container). you can use another container, and install `mono` on that. or directly use the fsharp docker container, who...

add with https://github.com/dotnet/templating/issues/954 the issue to add a `donet new template`

It's different, response files are useful mostly for tooling. as a note, windows has a max length for command line arguments. Tooling write args to a file, and invoke the...

The issue is that with VS 2017, now all extension who doesnt do async loading, are flagged as not responsive (that warning). Also R# and VF# was flagged 😄 like...

That's pretty much the time used by all extensions to start up, 8+ seconds. And whole extension, so some parts are reused by others extensions because shared that message is...

adding myself to discussion

@kjnilsson the search of fsproj is now supported fsac side (ref https://github.com/fsharp/FsAutoComplete/pull/191 ) and support also sln files. So should help implement this feature (just run `workspacepeek` at startup). Vim...

@Tombert i use WSL. i'd like to test vim plugin there. I'll followup when i try (soon). Are you sure you have `mono` installed? that's a requirement. the name is...

yes, you can run `./fsautocomplete.exe --help` and that will run as .NET process on windows. v-- `fsautocomplete.exe` invoked from WLS  problem is, FSAC doesnt check the OS atm for...

@Tombert but when in WSL, running FSAC in windows, is a nice use case. we can use all the windows .net tooling, and unix tools + unix vim. WSL: linux...