VSTAMajorVersion – SQL Server x Visual Studio
Hello,
Please, I need some help, on my machine I have installed:
1. SQL Server 2019 RTM- CU16 – GRD / catálogo environment with shared_component_version 15.0.4236.7
2. Visual Studio 2019 ( version 16.11.19) with Visual Studio tools for applications 2019 ( 16.0.3.1110)
When on VS 2019 I import a package from integration catalog (SQL 2019) the VSTAMajorVersion is equal 16.
If I try to open a script task from this package I get error message in Visual Studio 2019:
” XML: Sustem.Exception: The script Task ST_.……… 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 até converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_Product_Short_Name% Integration Services”.
And script task lost all code and configurations.
If I changed the VSTAMajorVersion to 15 in the code (XML) package before open script task works.
But it’s a problem: changed It all packages all the time after importes :(.
Ps: If I created a new package with script task the VSTAMajorVersion is equal 15 even though the TargetServerVersion property from my integration services project = ” SQL Server 2019″.
Hello, Please, I need some help, on my machine I have installed: 1. SQL Server 2019 RTM- CU16 – GRD / catálogo environment with shared_component_version 15.0.4236.7 2. Visual Studio 2019 ( version 16.11.19) with Visual Studio tools for applications 2019 ( 16.0.3.1110) When on VS 2019 I import a package from integration catalog (SQL 2019) the VSTAMajorVersion is equal 16. If I try to open a script task from this package I get error message in Visual Studio 2019:” XML: Sustem.Exception: The script Task ST_.……… 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 até converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_Product_Short_Name% Integration Services”. And script task lost all code and configurations. If I changed the VSTAMajorVersion to 15 in the code (XML) package before open script task works. But it’s a problem: changed It all packages all the time after importes :(. Ps: If I created a new package with script task the VSTAMajorVersion is equal 15 even though the TargetServerVersion property from my integration services project = ” SQL Server 2019″. Read More