title: Can I control the version of new SSDT reports in Visual Studio?
body: <p>I am using the Visual Studio SSDT BI add-on to create reports for SQL Server Reporting Services. The project I've created is configured to target SQL Server versions 2008/2012/2014, since those are the target SQL Servers our customers have.</p>
  
  <p>However, the report files being created within Visual Studio all appear to be targeting SQL Server 2016. If I copy the <code>rdl</code> files to another server and upload them via the browser, I am told that they are from a newer version of SSRS and can't be uploaded.</p>
  
  <p>The problem is the twofold:</p>
  
  <ol>
  <li><p>The <code>&lt;Report&gt;</code> tag contains a new 2016 namespace that replaces the 2010 one that existed in previous versions: </p>
  
  <pre><code>&lt;Report 
    xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner"
    xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" 
    xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition"&gt;
  </code></pre></li>
  <li><p>The new file format includes a parameters layout section that is defined in the 2016 namespace, but not in the 2010 one:</p>
  
  <pre><code> &lt;ReportParametersLayout&gt;
              .
              .
              .
   &lt;/ReportParametersLayout&gt;
  </code></pre></li>
  </ol>
  
  <p>If I change the namespace back to <code>2010</code> and remove the <code>ReportParametersLayout</code> section, the report works just fine in SQL 2012, but Visual Studio will put it back the next time I open the report.</p>
  
  <p>(Interestingly, if I deploy the reports directly from VS, I get a warning that the parameter layout is unsupported in 2012 and being removed, which implies that Visual Studio is fixing up the report definitions on the fly.)</p>
  
  <p>Is there any way to force VS to leave the report files in the previous versions format?</p>