?
Solved

Visual Studio 2015- Debugger breaks and says: "ProjectData.vb not found"

Posted on 2016-08-27
7
Medium Priority
?
171 Views
Last Modified: 2016-09-05
Just recently when I set a break point and tried to step through my code, I got a message that says "ProjectData.vb not found". It also says "You need to find ProjectData.vb to view the source for the current call stack frame."

I don't know what I may have changed to cause the debugger to look for this file because I used to be able to set a break point and then step through my code without this problem. I have searched my computer for the ProjectData.vb file, but it is not on my computer, and I don't know where to get a copy of the file. I have also done a Google search, but have not found the solution.

I also do not know which debug setting that the error message is referring to when it says:"The debug source files settings for the active solution indicate that the debugger will not ask to find the file: f\dd\vb\runtime\msvbalib\Helpers\ProjectData.vb. I don't even have an f drive on my computer.

Where do I find a copy of the ProjectData.vb file, or what setting do I need to set in the debugger to get the Debugger to stop looking for this file, if I really don't need it in order to step through my code? I need to be able to set break points in my code and then step through my code. I am hoping that someone may be able to help me.
0
Comment
Question by:Bob Valentine
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
7 Comments
 
LVL 3

Expert Comment

by:Dave
ID: 41773478
If it worked well before, I suggest you try to clean and rebuild your project, and then check it again. I am not very sure what's the real reason is. But it seems that your project need this file, if it is moved or lost, it will generate error, maybe you could check the path and make sure it has this file.

The above happened with me earlier, i tried the above and it worked.
0
 

Author Comment

by:Bob Valentine
ID: 41774007
Thank you Dave for your reply.

I tried cleaning and rebuilding my project, but that didn't fix the situation. I also tried repairing Visual Studio 2015 Community, and that didn't fix the problem either.

So, I finally decided that the only other thing to try was to uninstall Visual Studio 2015 Community and then re-install it. And that worked! I can now debug my code by setting break points and then stepping through the code by pressing F8, like I used to be able to do before the issue started. I must have had a corrupted file.

This might help others in the future that have a similar problem.
0
 

Author Comment

by:Bob Valentine
ID: 41774033
I spoke too soon! I still have the problem after uninstalling and then re-installing Visual Studio 2015 Community on my Windows 10 computer.

However, I do have it running correctly on my Windows 7 computer. I am having the issue with Visual Studio 2015 Community that is running on my Windows 10 computer. Maybe it has something to do with Windows 10. I do not know. I will have to keep on trying to solve the issue.

Anybody else have this problem on Windows 10 and found a solution? Or know what the fix is?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Bob Valentine
ID: 41774036
Please keep this question open, as I spoke too soon and I still have the same issue after re-installing Visual Studio 2015 Community.
0
 

Accepted Solution

by:
Bob Valentine earned 0 total points
ID: 41778407
I finally found out the resolution to the debug issue that I was having as explained in my prior original post of this question. I have found if you delete the .suo file from your project and then open your project, you should be able to press the F11 key and step through your code line by line without throwing the exception: ProjectData.vb not found, Operators.vb not found, etc.

This issue happened in my case because I transferred my project from one computer to another computer. The .suo file contains Specific user Options that may not be compatible with the other computer. Therefore, if the .suo file is deleted on the second computer the user options settings will be reset to the default settings.

I have attached a copy of the Solution Properties screen that shows the location of the Debug Source Files. It shows the source locations and the files that the debugger will not look for (locations on the f: drive).
Solution-Properties.pdf
0
 

Author Closing Comment

by:Bob Valentine
ID: 41784472
I am the original poster of this question and I found the solution to my Debug issue and have described what I did to fix the issue.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Well, all of us have seen the multiple EXCEL.EXE's in task manager that won't die even if you call the .close, .dispose methods. Try this method to kill any excels in memory. You can copy the kill function to create a check function and replace the …
Creating an analog clock UserControl seems fairly straight forward.  It is, after all, essentially just a circle with several lines in it!  Two common approaches for rendering an analog clock typically involve either manually calculating points with…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…
Suggested Courses

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question