title: Problems with Visual Studio 2013, TFS, and _references.js file
body: <p>We’re having an issue with Visual Studio 2013, TFS, and _references.js file.</p>
  
  <p>There are 3 of us on the development team.  We all have the following installed on our development laptops:</p>
  
  <ul>
  <li>Visual Studio 2013 Premium with Update 2</li>
  <li>Productivity Power Tools 2013 v12.0.30519.1</li>
  <li>Web Essentials 2013 for Update 2 v2.2</li>
  <li>Plus a couple other extensions, such as SideWaffle Template Pack.</li>
  </ul>
  
  <p>Our solution consists of an ASP.NET MVC project plus a couple other class library projects, and everything is checked into TFS.</p>
  
  <p>The problem we’re having is that the _references.js file gets automatically checked out when simply opening the solution and projects, even though no explicit changes were made to anything.  Then when one of the team members has the _references.js file checked out and the other team members just want to open the solution and projects, VS tries to checkout _references.js but can’t because it’s already checked out.  VS then throws up an endless number of message boxes with an error about not being able to check out the file.  The only way around it is to kill the VS process, make the person with the file checked out check it in, and then all team members can continue with their work.</p>
  
  <p>We can’t figure out why this is happen, and how to fix it.  Is it a VS 2013 thing?  Is there some setting to stop VS from automatically checking it out?  Is it a Web Essentials issue?  Basically, how can we stop this behavior since there will be client-side development time when one person needs to have that file checked out and this can’t prevent the other team members from working.</p>
  
  <p>Thanks!</p>