-
Notifications
You must be signed in to change notification settings - Fork 934
Upgrade AsyncGenerator to 0.17.1 #2182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -3,6 +3,8 @@ | |||
targetFramework: net461 | |||
concurrentRun: true | |||
applyChanges: true | |||
suppressDiagnosticFailures: | |||
- pattern: ^.*(Hql\.g).*$ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new version of Roslyn reports warnings for Hql.g, which have to be omitted.
It seems .NET Core support is also added in this version. Shouldn't we start using it right away? ) It's my understanding it would allow to skip installing mono for development process on Unix. |
Yes we could, the only reason I didn't use it is because the minimal .NET Core version is higher than what NHibernate has (
.NET Core would need to be installed instead. |
I personally see no issues with that. But maybe I don't understand all the implications. |
The only implication is that a developer with .NET Core 2.0 installed would be able to build the project but not able to generate the async code. I've changed the nant build to use .NET Core, |
@maca88, I was thinking about having a dotnet global tool. Is it feasible? |
Hi, I'm having issue on MacOS:
|
These work fine:
|
ok, this seems to be an issue with the dotnet sdk version. I wonder how can we fix it? |
Works for SDK 2.1.700. Does not work for SDK 2.2.300:
|
I also thought about it but then I realized that it would not work as a specific version may be required for a repository ( |
In .NET Core 2.2 |
@hazzik can you please verify if the current code works on MacOS? |
The current code does not compile on |
src/NHibernate.Test/Async/Tools/hbm2ddl/SchemaValidator/SchemaValidateFixture.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When re-generatig async (under Windows, latest VS 2017 (15.9.16), no VS 2019), the obsolete class FutureBatch
lose its GetResultsAsync
member, causing compilation failures.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Signed-off-by: maca88 <bostjan.markezic@siol.net>
307bc51
to
8f765cf
Compare
Upgraded to version |
This comment has been minimized.
This comment has been minimized.
English resource is embedded into project (see resource and project). And translations are provided as satellite assemblies. So I don't think that English localization can be omitted somehow. |
The version contains the fix for the issue discovered in #2056.
It also adds .Net Core support, and this PR switches the generation target framework to netcoreapp for better cross-platform development support.