The CLI package is not compatible with DotNet core 3.0

The CLI package is not compatible with DotNet core 3.0.

Because the dotnetTool package.

Severity	Code	Description	Project	File	Line	Suppression State
Error	NU1202	Package TypeGen.DotNetCli 2.4.2 is not compatible with netcoreapp3.0 (.NETCoreApp,Version=v3.0). Package TypeGen.DotNetCli 2.4.2 supports: netcoreapp2.2 (.NETCoreApp,Version=v2.2) / any	TypegenTest	C:\Users\agust\Source\Repos\TypegenTest\TypegenTest\TypegenTest.csproj	1	

Severity	Code	Description	Project	File	Line	Suppression State
Error		Package 'TypeGen.DotNetCli 2.4.2' has a package type 'DotnetTool' that is not supported by project 'TypegenTest'.				

[jburzynski]

Thanks, I’ll look more into this!

In the meantime, it should be possible to use the current version of TypeGen for .NET Core 3. If you run across any errors, please write here or in a new issue.

[jburzynski]

Glad I could help 👍

You can still use TypeGen with .NET Core 3 as long as you’re not using features specific to .NET Core 3 inside of the types you’re generating, which right now is probably the vast majority of the cases. If I upgrade, however, this would prevent people who use lower versions of .NET from using the newest TypeGen (and since the stable release of .NET Core 3 was a week ago, I felt that this would still be a lot of people). So just weighting the pros and cons I thought I’ll change the version of TypeGen in like 2-3 weeks so that the majority of people will have had the chance to upgrade by this time, but at the same time until TypeGen is upgraded, people who use .NET Core 3 could still use TypeGen, because they’re most likely not using the latest features inside the types they’re generating.

So at this point I’ll just wait a couple of days until most people have the chance to switch to .NET Core 3 and I’ll upgrade the version 😃 You’re right though that if the upgrade was delayed for too long, this would be bad, because TypeGen is a dev tool and it should allow you to use the latest features.