Rick Drizin

In case it helps someone, I've just built from [rkuris fork](https://github.com/rkuris/journey). In the readme of [my fork](https://github.com/Drizin/journey) I've added some instructions on how to build for Windows: - `go get...

I'm sorry for the poor/outdated documentation. The latest version of the sample template SimplePocos is [here](https://github.com/CodegenCS/Templates/tree/main/DatabaseSchema/SimplePocos) - and it doesn't require you to rebuild our forked version of System.CommandLine. All...

> Thank you for fast response! I was able to run the template using `dotnet-codegencs` CLI, but also would also have intellisense when I author the template. This forces me...

> I also stumbled upon a confusion around `ILogger` interface. Judging by name I expected the standard .NET logger, while it turned out to be your custom one. Microsoft ILogger...

> I forgot the reason I just remembered: logs can go to console (which doesn't need async) but they can also go to Visual Studio Output Window (which needs to...

> Now tried the same with your solution and see the same build error In the past I've published a nuget package which was refering to this private nuget dependency...

> I created my own project with the same dependencies as yours I've missed that. So.. probably you're pointing to the CSPROJ instead of using the NUGET, right? In this...

Ok, I found out what happened: CodegenCS.Models 3.0.0 was published with those bad references (System.CommandLine private version). After a few days, I noticed the problem and republished 3.0.1 fixed, then...

Sure thing. How would you call that class to avoid this confusion? I'll also investigate if I can replace my colorful console by the aforementioned Spectre.Console.

@Forge36 thanks for bringing this. I've just submitted [PR 1993](https://github.com/dotnet/command-line-api/pull/1993) with that improvement.