title: How to make setup file from project in VS2012 C#
body: <p>Recently I started programming in VS2012 C#, a Windows Forms Application and it is almost finished.</p>
  
  <p>I wanted to make a functional and good looking setup wizard
  So I searched the internet and stackoverflow and soon it became clear that NSIS is a program that has enough functionality to do the job for me.</p>
  
  <p>In VS2012 I have 3 options: Debug, Release and Publish</p>
  
  <ul>
  <li><p>Debug -  works fine on my computer and my program works but if I want to deploy on other machines I thing I need to reference some *.dll files, icons, help files, etc. which I need to distribute in the setup file (I think).</p></li>
  <li><p>Release - I think it's almost the same only a different folder.</p></li>
  <li><p>Publish - Makes the following files for me:</p>
  
  <pre><code>/publish/setup.exe
  /publish/PCWS-Report.application
  
  /publish/Application Files/PCWS-Report_1_0_0_0/FastReport.dll.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/FastReport.Bars.dll.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/ODBCMngr.dll.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/Image1.jpg.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/PCWS-Report.application.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/PCWS-Report.exe.manifest
  /publish/Application Files/PCWS-Report_1_0_0_0/PCWS-Report.exe.deploy
  /publish/Application Files/PCWS-Report_1_0_0_0/PCWS-Report.application
  /publish/Application Files/PCWS-Report_1_0_0_0/PCWS-Report.exe.config.deploy
  
  /publish/Application Files/PCWS-Report_1_0_0_0/Resources/
                                 Firebird_ODBC_2.0.1.152_x64.exe.deploy
  </code></pre></li>
  </ul>
  
  <p><strong>Finally my questions:</strong></p>
  
  <ol>
  <li><p>From which directory I take the files to build my Setup Files with?</p></li>
  <li><p>And if it is the Publish directory, do I need to rename the files?</p></li>
  <li><p>And do I need all the files, like the .manifest.deploy file or the .config.deploy etc.</p></li>
  </ol>