Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 27, 2015 1:58 AM
I am using Visual Studio 2015 Community. When I am using the debugger and stepping through my code, the debugger steps into code that is in the PropertyStore.cs and then says that it cannot find the Operators.vb and says to browse to find it. The Open File dialog opens and says that the original location was "f:\dd\vb\runtime\msvbalib\Helpers\Operators.vb.
I have an f drive but it is my external drive that I use for backups, so I am sure that the Operators.vb file was never located there. And, I never deleted anything on the f drive. I searched for the file on my C drive, but it was not found.
How do I get this file so I can properly use the debugger without this issue? Any help will be greatly appreciated. Thanks.
BobV365
All replies (2)
Thursday, August 27, 2015 2:29 AM âś…Answered
Pretty much a double post of this thread Debugger Question. Maybe a moderator can combine threads or something.
Regardless after searching again about this issue something similar except for a different filename occurs in this thread Visual Studio 2010 Debugging issue with Symbols, Can't find Conversions.vb file for VS 2010. Note at the link that the path info is similar to your issue except for the filename difference.
I suspect if you look at the two links in the answer to the question posted in the above link you will see info about Symbol Path and Microsoft Symbol Servers which I am not familiar with. I don't know that any of that will assist you though. Also you never answered questions in your previous thread and started a new one. I would suggest you answer the questions in your original thread.
Has this issue been occuring since you installed VS 2015 community?
Perhaps you should save your development settings to a file and then try resetting to default settings to see if the issue is resolved. If not you can then revert to the settings you saved to a file.
La vida loca
Thursday, January 30, 2020 7:09 PM
I had this suddenly pop up when trying to step through code. After trying a bunch of suggestions in settings, I concluded that an installed file was corrupted. I re-installed VS, choosing "repair" as the installation option, and that fixed my issue.