Skip to content

Conversation

@dennis-gr
Copy link
Contributor

Update NHibernate to 5.6 and remove usage of now obsolete methods.

@RogerKratz
Copy link
Collaborator

thanks!

@RogerKratz RogerKratz merged commit 396d8d9 into nhibernate:master Oct 16, 2025
7 checks passed
@RogerKratz
Copy link
Collaborator

btw, i was about to push a new nuget package but can no longer get async generator work locally. are you aware if something has changed there?

@dennis-gr
Copy link
Contributor Author

btw, i was about to push a new nuget package but can no longer get async generator work locally. are you aware if something has changed there?

It's working fine for me with the following commands:

dotnet tool restore
dotnet restore
dotnet async-generator

BTW, I've opened another PR #57, maybe you could take a look at it before doing the release.

@RogerKratz
Copy link
Collaborator

dotnet async-generator in my env =>

AsyncGenerator.CommandLine[0]
Visual Studio installation directory was not found. Install Visual Studio or set the environment variable VSINSTALLDIR
System.InvalidOperationException: Visual Studio installation directory was not found. Install Visual Studio or set the environment variable VSINSTALLDIR
at AsyncGenerator.Internal.EnvironmentHelper.Setup() in C:\Workspace\Git\AsyncGenerator\Source\AsyncGenerator\Internal\EnvironmentHelper.cs:line 120
at AsyncGenerator.CommandLine.Program.Main(String[] args) in C:\Workspace\Git\AsyncGenerator\Source\AsyncGenerator.CommandLine\Program.cs:line 39

This happen even in dev command prompt where %VSINSTALLDIR% defiantly is available.
What has changed since I last created a release is that im on a fresh computer environment. VS2022 only (+rider).
Any clue? thanks.

@RogerKratz
Copy link
Collaborator

...after merging #57 it works fine for me it seems. Some fix in upgraded async-generator probably did the trick!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants