Maybe someone has suggested this already, but I'd love to see a script repository, i.e. global/reusable script code in the same way Connections and Credentials are.
Thinking simply, the implementation would be a cross between the .NET script and assembly execute tasks, i.e. create the script like we do in script task, but use it like an assembly execute task. Perhaps the assembly execute dialog could be modified to provide a dropdown to choose a assembly compiled from the scripts in the repository.
The names in the dropdown should be friendly...maybe this is solved by requiring us to include namespace in repository scripts. Then maybe namespace affects compilation, almost like a VS solution and its projects. Just thinking out loud here. I'm sure something elegant could be developed.
And we'll stay DRY (don't repeat yourself) by not having copies of the same script code in different tasks.
Edited by moderator
2019-04-30T08:01:36Z
|
Reason: Not specified