We're building an ETL Product in SSIS. A lot of our SSIS packages have script tasks written in C# script with assembly references to Microsoft.SqlServer.ScriptTask, Microsoft.SqlServer.ManagedDTS etc.
Some of our customers may be using an older version of SQL (2014) while some may upgrade to 2016.
What is the industry standard and best practice for such situations, where you can release newer product versions to both set of customers using old and new SQL Server versions?
Is there any way we can support both SQL Server 2014 and 2016 without having to maintain 2 code bases?