Closed fredericDelaporte closed 4 years ago
Or is there anything else to do to fix this trouble, like a way to instruct the generator to use the 2.1 SDK instead of 3.1?
you can instruct to use a lower SDK version by adding a global.json
file in the root NHibernate folder. Mine contains:
{
"sdk": {
"version": "3.1.100"
}
}
I do the same. But I set 2.1.700.
Ok, thanks. I have put 2.2.109, as I have 2.1.516 at most in 2.1 series, and it fixes the trouble. I have put this above the NHibernate root, to avoid having the file detected by git.
So I guess this issue will actually be fixed by #146. Closing.
We may commit the workaround into NHibernate, with something like:
{
"sdk": {
"version": "2.0.0",
"rollForward": "latestMinor"
}
}
But as the rollForward
property is a 3.0 SDK thing, it will not work for those not having any 3.x SDK, unless they have precisely a 2.0.0 SDK. So for some people it may cause troubles instead of helping.
I have removed VS 2017 and installed VS 2019 today, and now the async generation of NHIbernate fails with this error log (some parts, put between
{}
, have been translated to English by me):I have seen #146 about adding support for .Net Core 3.1. But I still have .Net Core 2.1 installed too. And attempting to remove 3.1 from the Visual Studio Installer asks for removing almost all of VS2019.
Is #146 required for being able to use the async generator when .Net Core 3.1 is installed? Or is there anything else to do to fix this trouble, like a way to instruct the generator to use the 2.1 SDK instead of 3.1?