title: best content on how to deploy and share a VSTO solution
body: <p>with the push to leverage visual studio and dotnet with office based solutions, especially excel, where is the best article or information on how having office sheet with additional binaries and assemblies is sharable.  </p>
  
  <ol>
  <li>Do this external code get packaged with the spreadsheet</li>
  <li>what if people start emailing the spreadsheet around.  Is there any overhead of this additional assemblies.  Is there risk of the binaries getting detached from the spreadsheet</li>
  </ol>
  
  <p>It seems like <a href="http://www.devx.com/OfficeProDev/Article/28088" rel="noreferrer">microsoft has been pushing VSTO for over 5 years now</a> but you read lots of mixed reviews and issues.  Are we at the point where companies that do large VBA excel solutions can fully migrate over to dotnet without any real worries?</p>