• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 1033 views
  • Users 0 members are here
Options
Related

Vaidate Custom Development with Community 13

Stephen Vicino

Is the tool available to highlight what needs to change in the Custom Plugin code? I remember hearing about this a while back as with the .NET upgrade comes a bit of updates that need to be made against custom plugin code.

Parents
  • 0

    Community 13 does not require a .net version update, however, Community 14, when released, uses .net Core (currently and likely .net 9.0). This .net version change will require compiled customizations (plugins) to be updated and recompiled.

    To prepare for the upgrade to Community 14 and .net Core, the following tasks can be completed to make the migration easier for compiled customizations (plugins):

    1. Ensure that your custom code, when built against Community 13, has no obsolete warnings.
    2. Ensure that your custom code only uses supported APIs and database access. Supported APIs are the ones documented ( API Documentation ) and generally exist within the Telligent.Evolution.Extensibility namespace. Supported database access is limited to the te_v1_permissions_EffectivePermissions view.

    Customizations made with scripting or against the REST API will not require any updates. Plugins that meet the two guidelines above will still need to be migrated to .net core prior to the upgrade to Community 14, but, that migration will be easier if these two tasks are completed beforehand.

  • 0 in reply to Ben Tiedt

    Thanks for the info Ben. Any idea when v14 might be released.. even if it's quite vague (like Q4 2025)?

Reply Children
No Data

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community