MySql 5.7 service and path not found anymore on "Visual Studio 2022" image

[fredericDelaporte]

Since a few days, NHibernate AppVeyor builds are failing their MySql run.

Our yaml uses a database matrix and starts only the required database for the run.

For MySql, that is:

        Start-Service 'MySQL57'
        # Create nhibernate database (not handled by NHibernate.TestDatabaseSetup.dll)
        $env:MYSQL_PWD = 'Password12!'
        & 'C:\Program Files\MySQL\MySQL Server 5.7\bin\mysql' -e 'CREATE DATABASE nhibernate CHARACTER SET utf8 COLLATE utf8_general_ci;' --user=root

But this has started to fail six days ago. We use the "Visual Studio 2022" image.

The build fails to find the MySql service and its path.

Start-Service : Cannot find any service with service name 'MySQL57'.
...
Command executed with exception: The term 'C:\Program Files\MySQL\MySQL Server 5.7\bin\mysql' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

An example failure is here. A previous successful build with same configuration is here.

[dennis-gr]

According to this Visual Studio 2022 now includes MySQL 8.0 (which makes sense since 5.7 has reached EOL).

[fredericDelaporte]

Thanks for the link, But the documentation still states that is the 5.7 version which is included, and there is no announcement about this change in the update page.

So, it looks like there was no way to plan for this apparent breaking change. And we cannot even be certain of the right course of action to take since the change is not yet actually documented.

[OwenMcDonnell]

Apologies, merging of the PR for the documentation somehow slipped through the cracks, although the updates had occurred a couple weeks prior.

[fredericDelaporte]

Ok, thanks.