title: Application deployment to network drive
body: <p>I have a <code>.NET 4</code> <code>WPF</code> application that needs to run inside a company network.<br>
  The application does not use local files (it does have an <code>app.config</code> file but it only contains some <code>connection strings</code>)  for data storage but a central <code>SQL server</code> database.
  What are the downsides of putting the application files on a shared network drive and just creating a shortcut to the application executable for each user?<br>
  I've found some data on the subject in the following links but I couldn't get a clear answer:<br>
  <a href="https://stackoverflow.com/questions/439515/run-a-net-program-from-a-mapped-drive-or-shared-folder-pros-cons">Run a .NET program from a mapped drive or shared folder - Pros/Cons</a><br>
  <a href="https://stackoverflow.com/questions/359978/run-a-net-program-from-a-mapped-drive-or-shared-folder">Run a .NET program from a mapped drive or shared folder</a><br>
  <a href="http://support.microsoft.com/kb/832742" rel="nofollow noreferrer">http://support.microsoft.com/kb/832742</a><br>
  It would also be nice to know how stuff works when using this approach, are the application files being copied to the local user or something else happens?</p>