title: Source Control advice across multiple developers using a shared folder
body: <p>I am looking for some general advice on source control.  Currently we have multiple developers running from a shared drive (connected to IIS) - Dev platform (.NET). </p>
  
  <p>We are looking to implement source control via bit bucket, but my question is.  Does each developer need their own instance of the application code or can they still run from a share?  The issue being that when making edits, source control or not, they are editing the same environment (dev).   </p>
  
  <p>Should it be that they have their own instance (this is a big application) locally or via their own share and then changed deployed to a central area once completed and ready for test.</p>
  
  <p>Obviously the second concept is a lot more work to deploy but as we scale i would prefer the best option. </p>
  
  <p>Your feedback and guidance would be greatly received. </p>