Skip to main content

Vertigis Studio Workflow Server side Custom Activity with Sql server connection

Comments

3 comments

  • Ken Lyon

    Hi Than Aung ,

    Thanks for your question.

    You might need to treat Microsoft.EntityFrameworkCore.SqlServer and Microsoft.Data.SqlClient as external references according to this article. If they're not currently used by Workflow Server, you'll need to copy them to the “C:\Program Files\VertiGIS\VertiGIS Studio Workflow\CustomAssemblies” directory (assuming you chose the default installation location) along with your activity pack.

    That should get you unstuck in the short term.

    In the long term, I can migrate us from System.Data.SQLClient to Microsoft.Data.SqlClient in a future release.

     

    1
  • Than Aung

    Thanks Ken,

    Yes, I have followed the article you mentioned, and it successfully copied all the referenced DLLs into the custom assemblies folder. But it is not working.

    I tried and modified the application design to use a .NET Standard 2.1 library, with direct references to EF 6.4, EF 6 SQL Server (which is no longer supported by Microsoft) to VertiGIS and the System.Data.SqlClient NuGet package. This setup is working well.

    However, I would like to transition this application to .NET Core.

    Any guidance on how to achieve this would be greatly appreciated!

     

    Best Regards,

    Than

     

    0
  • Ken Lyon

    Hi Than Aung ,

    I think you should be able to use .NET Core, although I don't know if I've tried that for an activity pack. I can tell you that Workflow Server itself is currently targetting .NET 8.0. You should probably match that for the best chance of it working.

    0

Please sign in to leave a comment.