Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 290
  • Last Modified:

How to fix this debug exception: Operators.vb not found.

I am having a problem with the debugger in Visual Studio 2015 Community on my desktop Windows 10 PC. When I set a breakpoint and then Step Through my code by pressing the F8 key (Step Into), when I come to the following code: "If Method = "MACRS Then",  I get the following message: "Operators.vb not found. You need to find Operators.vb to view the source for the current call stack frame. Locating source for f:\dd\vb\runtime\msvalib\helpers\Operators.vb." I have searched my hard drive for the Operators.vb file, but cannot find it anywhere. (I do not have an F drive, and never did.)

I have Visual Studio 2015 Community on my laptop and the debugger seems to step over that same line without throwing an exception. So I compared the two debug exception settings and set them the same, but this did not fix the problem on my desktop version. I also did a search on my laptop to see if I could find the Operators.vb file and copy it to my desktop PC, but I did not find the Operators.vb file on my laptop either.

I have Cleared and then Rebuilt my application, but this also did not fix the problem. I even deleted and then re-installed Visual Studio 2015 Community, and that also did not fix the situation.  I have searched the internet for solutions, but there was no help there either. The topics that seemed to be right on topic had no solution, just the question.

This is frustrating because it seems like it should be a simple fix, a debug setting, or something similar, but I can't figure it out. Any help will be greatly appreciated.
Operators-vb-Not-Found.pdf
0
Bob Valentine
Asked:
Bob Valentine
  • 3
1 Solution
 
TechieMDCommented:
Go to Tools->Options->Debugging->General and then click the Step Over Properties And Operators (Managed Only) checkbox.
0
 
Bob ValentineCPA / Owner - Cellutionware SoftwareAuthor Commented:
TechieMD, thanks for your help. However, when I looked at the Step Over Properties And Operators (Managed Only) exception setting, the checkbox was already checked. So unfortunately for me, this does not fix the problem I am having with the debugger in Visual Studio 2015 Community.

Any other suggestions for help in fixing the debugger so that it will be able to find the Operators.vb file? BTW, the debugger also asks for ProgramData.vb when it encounters other lines of code. What is going on? I can't be the only person who has ever encountered this problem, or can I?
0
 
Bob ValentineCPA / Owner - Cellutionware SoftwareAuthor Commented:
I finally figured out the root of the problem. The problem was created after I transferred my VB.Net project file from one PC to a second PC. The problem was contained in the .suo file. I learned that this file contains option settings for a specific user on a specific PC.

So I deleted the .suo file and opened my project in Visual Studio 2015 Community and now I was able to press the F11 key to step into my code line by line without throwing a debug exception that looks for the Operators.vb file and others. I also went to Tools>Options>Debugging>General and checked the Enable Just My Code checkbox so that the debugger is only debugging my code.

So all is good. I hope this will help others who might transfer their project (including the .suo file ) to another developer's PC and then have the same problem that I did with the debugger.
0
 
Bob ValentineCPA / Owner - Cellutionware SoftwareAuthor Commented:
My solution solved the debugging issue that I was having after transferring my project files to a second computer.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now