SSIS solution edited on VS 2019 Enterprise can't be opened on VS 2019 Pro

Thanks Mona - When I rebuild the script I get 14 errors, but they can be condensed down to:

The type or namespace name 'ScriptBuffer' could not be found (are you missing a using directive or an assembly reference?) sc_56ed69b65c7a487fbb9ed447226ff3b5 C:\Users\Antony\AppData\Local\Temp\Vsta\SSIS_SC140\Vsta09ab9AF__OEueNUl1h88OvA\VstaO0aq6jAWDUWv3yNUlT3bKQ\BufferWrapper.cs

-- Detail only for the rest.There's one of these for each relevant line in the code:
... The type or namespace name 'OutputNameMap' could not be found (are you missing a using directive or an assembly reference?) ... \BufferWrapper.cs

The type or namespace name 'ScriptComponent' could not be found (are you missing a using directive or an assembly reference?) .... \ComponentWrapper.cs

The type or namespace name 'OutputNameMap' could not be found (are you missing a using directive or an assembly reference?) ..... \ComponentWrapper.cs

and then .....

Error The type or namespace name 'SSISScriptComponentEntryPointAttribute' does not exist in the namespace 'Microsoft.SqlServer.Dts.Pipeline' (are you missing an assembly reference?) sc_56ed69b65c7a487fbb9ed447226ff3b5 C:\Users\Antony\AppData\Local\Temp\Vsta\SSIS_SC140\Vsta09ab9AF__OEueNUl1h88OvA\VstaO0aq6jAWDUWv3yNUlT3bKQ\main.cs 14
Error The type or namespace name 'SSISScriptComponentEntryPointAttributeAttribute' does not exist in the namespace 'Microsoft.SqlServer.Dts.Pipeline' (are you missing an assembly reference?) sc_56ed69b65c7a487fbb9ed447226ff3b5 C:\Users\Antony\AppData\Local\Temp\Vsta\SSIS_SC140\Vsta09ab9AF__OEueNUl1h88OvA\VstaO0aq6jAWDUWv3yNUlT3bKQ\main.cs 14
Error 'ScriptMain.PostExecute()': no suitable method found to override sc_56ed69b65c7a487fbb9ed447226ff3b5 C:\Users\Antony\AppData\Local\Temp\Vsta\SSIS_SC140\Vsta09ab9AF__OEueNUl1h88OvA\VstaO0aq6jAWDUWv3yNUlT3bKQ\main.cs 20

Thanks Mona, but it is most definitely a script component, and has been for about 5 years, (written in VS2013). It was working in VS2019 Enterprise. It's only when I had to re-install VS 2019 as a Professional version that the problem started; when I opened the project in VS2109 Pro, the package showed errors in two of the three script components. Neither had been changed in any way. I have added a new script component to one data flow, and copied the C# code to it, and after a lot of tinkering with inputs/outputs, it now works. However the other one is more complex, and I don't want to have to go through all of that again. However there's evidently some kind of a problem with converting packages from VS 2019 Enterprise to Pro. Tho objects that it seems to have a problem with, (namely BufferWrapper.cs and ComponentWrapper.cs), definitely exist, so it seems that VS2019 Pro doesn't understand them for some reason.

Are you using the latest SQL Server Integration Services Projects ?
The latest version is 3.9

Hi AntoDN,

May I know if you have anything to update?

Best Regards,
Mona

Hi - The version is 3.8, from July 2020.

Update on this page, or my package? My answer from yesterday still stands, but it seems to me that the only option is to start again, and copy and paste the C# code from the old script component to a new one. I muddled on for years with VS 2013 because the upgrade was so unreliable, but I braved it to go to VS2019, but my fears are realised again. Does it really have to be so complicated and unreliable? My packages are hardly complex - just run of the mill ETL packages.