Visual Studio upgrade from 16.11.15 to 16.11.18 -C# script task code missing

Ben Pflanzer 0 Reputation points
2023-04-27T17:11:11.74+00:00

I have developed some SSIS projects using VS 16.11.15 and deployed to SSISDB on SQLServer Standard 15.0.4261.1.
TargetServerVersion = SQL Server 2019.
After upgrading Visual studio to 16.11.18, importing the project from SQLServer, every script task in the project fails giving the following error:

There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_45190de147e941b3adfc470f9e283a4f" uses version 16.0 script that is not supported in this release of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts are converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration Services.

Additional information:
I can export using SSMS to an ISPAC file and it will work successfully, but that's not efficient.
I can also import the same project from Sqlserver into Visual studio version 16.11.15 and everything is fine.

Developer technologies | Visual Studio | Other
{count} votes

2 answers

Sort by: Most helpful
  1. Tianyu Sun-MSFT 34,446 Reputation points Microsoft External Staff
    2023-04-28T13:42:02.0933333+00:00

    Hello @Ben Pflanzer ,

    Thank you for taking time to post this issue in Microsoft Q&A forum.

    There’s a common issue, see this document: Common issues

    Sometimes this product or Visual Studio Tools for Applications 2019 may be somehow deleted during VS instance upgrade. If your existing SSIS projects cannot be loaded, try to repair this product via control panel.

    I suggest first try to repair SSIS extension from Control Panel > right-click Microsoft SQL Server Integration Services Projects > Uninstall/Change > Repair.

    If it doesn’t work, please kindly click Help > Send Feedback > Report a Problem… and directly report this issue on our Developer Community with VS Product Team to investigate further.

    Feel free to let us know the results.

    Sincerely,

    Tianyu


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Ben Pflanzer 0 Reputation points
    2023-04-28T16:57:23.8533333+00:00

    I resolved this by reverting integration services projects to V 3.16
    File version 15.0.2000.180 (from 4/11/2022)
    This solved 3 problems I was having:

    1. This issue where the code and variables for script tasks disappear
    2. Can't import directly from SQLServer 2014 (yes, our ETL server is old, we're working on it)
    3. minor annoyance: projects default to targetserverversion 2022

    Thanks


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.