You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using RH library in .NET 5/6, the following error happens:
Unable to copy ./Scripts/db1/OneTime/YYYY-MM-DD-Initials-JiraTicket-1-SampleRoleCreation.sql to ./Scripts/db1/OneTime.
System.DllNotFoundException: Unable to load shared library 'kernel32' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libkernel32: cannot open shared object file: No such file or directory
at roundhouse.infrastructure.filesystem.DotNetFileSystemAccess.CopyFileA(String lpExistingFileName, String lpNewFileName, Int32 bFailIfExists)
at roundhouse.infrastructure.filesystem.DotNetFileSystemAccess.file_copy_unsafe(String source_file_name, String destination_file_name, Boolean overwrite_the_existing_file)
at roundhouse.runners.RoundhouseMigrationRunner.copy_to_change_drop_folder(String sql_file_ran, Folder migration_folder)
at roundhouse.runners.RoundhouseMigrationRunner.traverse_files_and_run_sql(String directory, Int64 version_id, MigrationsFolder migration_folder, EnvironmentSet migrating_environment_set, String repository_version, ConnectionType connection_type)
There is handing for Mono & .NET Core, but with .NET 5 the Core naming has been dropped.
I see this deliberation here, but has anyone tried to at least support use of libraries in .NET 6? I don't believe that would require upgrading the project to .NET 6 and it might be just this one place to fix.
When using RH library in .NET 5/6, the following error happens:
The issue is here:
roundhouse/product/roundhouse.core/infrastructure/filesystem/DotNetFileSystemAccess.cs
Line 20 in 0f17f69
There is handing for Mono & .NET Core, but with .NET 5 the
Core
naming has been dropped.I see this deliberation here, but has anyone tried to at least support use of libraries in .NET 6? I don't believe that would require upgrading the project to .NET 6 and it might be just this one place to fix.
.NET 3.1 End of Support is at the end of 2022: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
The text was updated successfully, but these errors were encountered: