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

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

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


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

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 6/1/2016 at 8:59 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.
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.