title: visual studio 2013 local variables not showing in debugger
body: <p>I have a solution written in VB with some C# components. The solution uses some libraries from 2 outside sources. I have been working on this project for several months without issue. I cannot identify anything specific that I did to change my system or configuration. I was just working through the code, transitioning from an old set of library calls to the new library calls. The new library calls require complete rewrite so I change sections of the code and test to that point. Visual Studio 2013 debugger as of Friday morning will no longer recognize or show my local variables in this solution. The only things that appear in the Locals window are under Me. The code does work and I have it writing out to a text log file to confirm the values of variables at certain points, but the debugger has gone blind. When I add any of these local variables to Watch the response is " is not declared. It may be inaccessible due to its protection level."</p>
  
  <p>Steps I've taken so far with no permanent success:</p>
  
  <ul>
  <li>looked online and tried the few matches I found with no success</li>
  <li>deleted the bin and obj folders and had the solution rebuild with no
  success</li>
  <li>recreated solution from scratch, copied over base files and rebuilt
  solution and project (which worked for a few hours), until I did a
  rebuild project and problem appeared again</li>
  <li>updated to pack 5 and no success</li>
  </ul>
  
  <p>I have opened my older projects and checked them. The debugger runs just fine and shows the variables. It is obviously something that happens during the rebuild process.</p>
  
  <p>Any assistance would be greatly appreciated.</p>
  
  <p>Thanks</p>
  
  <p>Update:
  Let me try to explain a little more clearly the situation.</p>
  
  <p>I have an application I have built and am selling to some customers. Version 1 is installed and running at several locations. It is written in VB and uses some older COM libraries for a particular integration process.</p>
  
  <p>The vendor is retiring the COM libraries. Their new libraries are in C#.</p>
  
  <p>I created a new copy of my entire application (solution) and imported the new C# libraries. I have been going through and replacing the old code with the code for the new calls.I recompiled the solution and everything ran fine in debug.</p>
  
  <p>The objects used with the new calls are completely different and there is limited documentation so I update a section of code and test to that point. Each time I "Save all Files", rebuild the project and test the changes. Everything worked fine for a few days. On Friday morning I started working on more changes and got an odd error. The system was not getting a proper value for a certain variable. When I went to check it in the WATCH window, debugger said it could not evaluate it. I figured something was hung up so I shut everything down and rebooted my machine. When I tried it again later, the same problem.</p>
  
  <p>After several hours of no success I exited VS, renamed the folder to "OLD" and recreated the solution from the older version. Immediately everything was looking fine. I started making the changes and testing. Each time I did a rebuild, everything looked fine until the last change. Here I am again.</p>
  
  <p>The code works fine up to the point I have updated. The only issue is that the debugger windows are not working correctly. If a variable is declared at the Class level outside the Sub, they can be seen. The only variables the debugger is blind to are the local variables within the running Sub.</p>
  
  <p>I looked for anyone else with this issue and only found a few items. I tried the suggestions but no joy. I am left with having to temporarily define the variables outside the sub so I can see them while debugging.</p>
  
  <p>I am on VS 2013 Update 5.</p>
  
  <p>Do I need to move to VS 2015 to get around this?</p>
  
  <p>Thanks again for your time and assistance.</p>