Elsa3.1.0 package dependency

[daconglee]

Elsa3.1.0 package dependency

[glime-ai]

To address your issue with the MySqlConnector package causing compilation problems in your PostgreSQL-based project, it's important to understand that Elsa Workflow might have dependencies that are not directly used in your project but are included as part of the broader Elsa package suite. This can happen when a library is designed to support multiple database providers, and it includes the necessary drivers for each supported database as dependencies.

If you are not using MySQL in your project and you are certain that the MySqlConnector package is causing the compilation issue, you can try a few things:

1. Ensure that you are referencing the correct NuGet package for PostgreSQL. For Elsa Workflow, you should be using Elsa.Persistence.EntityFrameworkCore along with Npgsql.EntityFrameworkCore.PostgreSQL.

2. Check your project file to see if the MySqlConnector package is explicitly listed and remove it if it's not needed.

3. If you are using package management tools like NuGet, try restoring your packages to see if that resolves the issue.

4. Since you mentioned that you do not have internet access, make sure that all the necessary packages are available locally or in a local NuGet feed that your build process can access.

5. If the issue persists, consider reaching out to the Elsa Workflow community or checking their GitHub issues for similar problems and potential solutions.

Since you are using .NET 6.0, ensure that all the packages you are using are compatible with that version.

If you need further assistance, please provide more details about the error messages you are receiving during compilation, and I will do my best to help you resolve the issue.

[Suchiman]

Duplicate of #5158

[Suchiman]

Should be resolved as of version 3.1.2 @daconglee

[sfmskywalker]

As per @Suchiman 's remark, this is now fixed. Thanks for reporting @daconglee , and many thanks @Suchiman for the fix 👍🏻