Ali Bahrami

I would love to contribute and update the old template to a new and working one. I couldn't find the source for the VSIX though.

I managed to upgrade the project, now [it supports VS2019](https://github.com/0x414c49/Accessories/commit/f723ba909d2a3d30343c1bab26fb713e63ead92c). VSIX packages can be accessed here: https://github.com/0x414c49/Accessories/tree/vs2019/templates/visual%20studio Seems the source code inside accessories repo is kinda outdated. I don't talk...

Builds are failing on Travis and AppVeyor because of the .NET SDK and Mono version. I need to see how to fix them.

- Travis-ci: Distro has changed to Ubuntu bionic, Mono changed to 6.8.0 and dotnet SDK to 3.1.102 - Appveyor: image changed to VS2019 - PowerShell script: CakeVersion updated to 0.37.0...

There is something interesting, Travis CI now supports .NET SDK 3.x.x by default. Why do we need to install it again?

By replacing `AsyncUsageAnalyzers` with `Microsoft.VisualStudio.Threading.Analyzers` there are +500 warnings about async usages. They are mostly in test projects.

The pipelines now compile fine. The tests are running fine Linux, OSX and on a local-machine. `BrowserFixture.Should_return_JSON_serialized_form` is failing on AppVeyor.

I don't know why. I have a parallel test on my own AppVeyor account. The tests are passing fine [there](https://ci.appveyor.com/project/0x414c49/nancy/builds/31422801/tests)! 

By rerunning the build, everything works fine.

@khellang you are right about the `APIs`. It's not a must but shouldn't keep the project updated to be able to use the latest APIs? like support for `Span` in...