SSDT (SSIS packages) shouldn't save the layout information in one file with the actual package logic - by Andrej Kuklin

Status : 

 


27
0
Sign in
to vote
ID 752568 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 7/6/2012 2:29:19 AM
Access Restriction Public

Description

Currently development of SSIS packages is very source-control-system unfriendly. I'll just copy my feedback from the blog of Matt Masson.

http://www.mattmasson.com/index.php/2012/02/thoughts-on-branching-strategies-for-ssis-projects/

Layout is visual, client-dependent information. It can be even regenerated by BIDS/SSDT automatically. It's pretty unfortunate that this information is placed in one file with the actual package logic and human intervention is needed each time the decision needs to be made whether it was a code-relevant change or not.
Comparing to .NET/C# development, Visual Studio guys made a great usage of partial classes and moved the layout, generated by the designer into *.Designer.cs files. BIDS/SSDT would definitely benefit from a similar, modular approach.
Sign in to post a comment.
Posted by Microsoft on 8/27/2012 at 9:03 PM
Thank you for your feedback. We are actively looking at the issue and will keep you updated.