It seems that in the 2016 SSIS tooling, if you open a package and the task cannot be found, the package XML is changed and any invalid creation name references are replaced by "SSIS.ReplacementTask". So if I then fix the issue, such as installing the missing task, I'm still stuck with a broken package, because nothing changes "SSIS.ReplacementTask" back to "NowInstalledTask" or whatever it was before.
Have I misunderstood this, or was this a by design that the designer will corrupt your package, and assume you have your own backup to revert to?
Thanks
http://www.sqlis.com | http://www.konesans.com
