title: How to deploy RDLC files with visual-studio 2010 setup
body: <p>I am developing a windows app where many <code>.rdlc</code> are there in a "report" folder of that project. When I create a setup for delivery to the client, do I need to include all those .rdlc file manually or will they be included automatically just like .rpt (crystal report) files?</p>
  
  <p>What I could do: as a result always include .rdlc files automatically, when I batch build my project. Can anyone guide me?</p>
  
  <p>I asked the same thing in another forum and got the following guidance:</p>
  
  <blockquote>
    <p>...found that reports tend to grow, usually AFTER the application has been deployed and has been used for some time. Also if you have different customers they often want distinct reports.</p>
    
    <p>I had all my reports in a table, all records had a stored procedure name and a file name, if the file existed and the procedure existed the report could execute.</p>
    
    <p>I could then distribute a new report without having to recompile and distribute the app. Simple deliver the file and a script to create the stored procedure and report record.</p>
  </blockquote>
  
  <p>But I want to know about <em>RDLC</em>, which is client side. I asked how I could distribute my <code>rdlc</code> files with my application setup, so that as a result when a client installs my setup he can view the report which is based on rdlc. I'd like to know what (if any) is the industry standard for including rdlc files into a setup project. If anyone knows about such a thing then please advise me.</p>