tietoevry / ntypewritercli Goto Github PK

Internally reported. Seems that creating a workspace is what's slow - neither of us are sure exactly what causes it, or what triggers it.

It would be great to have compatibility tests with the VS extension - basically a small .NET Standard project with some templates, and a folder with the output from the extension. We could then, in a test, compare that with the CLI output. We should aim at 100% text similarity (the same text in files, but encoding might differ, because VS loves UTF-8-BOM).

There's not a lot of work here - a mock project and Visual Studio so you can use the extension to generate templates. It probably won't match, but that's out of scope for this item.