Change the way Script Task/Components are handled in SSIS
When having to work with script task or components inside of SSIS it becomes quiet tedious because the loading times are exessive and the functionalities are rather limited.
I would like to propose a new form of Script Task, a Script Task v2 if you will. Instead of just exposing a subset of VS making this Script Task a proper C#/VB.net proj that compiles down to a dll. That has a Main Class that implements an interface that contains a execute-method.
These Projects would be added to the SSIS Solution as seperate Projects offering everything from Nuget to properly allowing Version Control of the code within them. This would also allow proper Code reuse through just allowing the same DLL to be called from different places inside the Control or Data Flow inside the Package and different Packages inside the SSIS Project.
This would add tremendous value for the people with a Software Development background and would support more complex usecases with less friction.