Binary was not built with debug information

Question

Hi,

I have a visual studio 2015 solution (Version 14.0.25123.00 Update 2) targeting .net framework 4.5.2 as an x86 application.
The solution consists of a winforms project and an install shield project.

I'm trying to run the app in debug where I can put break points in the code but i'm experiencing the following issue:

When I rebuild and run the app under the window - Debug->Windows->Modules I can see for my project name (the .exe file) the path is correct to the .exe file:
C:\LineApp\Visual Studio 2008\Projects\EngineService\lineSQLEngine\lineSQLEngine\bin\x86\Debug\LineSQLEngine.exe

Under the symbol status section I can see the message 'Binary was not built with debug information'.
If I look in the above path i can see that the file LineSQLEngine.exe and LineSQLEngine.pdb have been generated.
I've also noticed in the same  Debug->Windows->Modules window I can see under the name column an item called '?' with path '?' again under the symbol statsus section I can see the message 'Binary was not built with debug information' .
(i'm not sure if this is relevant)

I've tried the following:

1. Checked all settings are set to debug. x86 as per existing posts on forums.
2. Deleted obj and bin folders and performed clean and rebuild of project.
3. Ensured that 'Enable Just My Code' is not selected.

I'm stuck here to debug my code so any help would be appreciated.

Regards,

Kevin

Answer 1

Hi Kevin,

Thanks for your posting.

>>When I rebuild and run the app under the window - Debug->Windows->Modules I can see for my project name (the .exe file) the path is correct to the .exe file:
C:\LineApp\Visual Studio 2008\Projects\EngineService\lineSQLEngine\lineSQLEngine\bin\x86\Debug\LineSQLEngine.exe

base on the path info as above shown, is this project migrated from VS2008? Does this happened to the new project(created by VS2015) as well?

>>Under the symbol status section I can see the message 'Binary was not built with debug information'.

this error message means:

The dll you are trying to debug most probably is not being built in your solution. You need to locate where it is being built and obtain a debug version.  Make sure you set the Debug mode other than release.

If your project is already in Debug mode. Please check Advanced Build Settings Dialog Box in Build tab of project.

Make sure that Debug Info is not set to none 

Btw, actually, the latest update of VS2015 is update 3, so I really recommend you update it, which I more robust and fixed several bugs.

Hope above helps.

 

Best regards,

Fletcher

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Hi Kevin,

Any update of this issue?

Please feel free to let us know if you need more help.

 

Best regards,

Fletcher

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 3

Hi Fletch,

Thanks for your response. In my system I do not have a 'build' tab in 'my project' properties.

Instead I have a 'Compiler' tab and I pressed the 'Advanced Compiler Options' button.

The equivalent setting'Generate Debug Info.' is already set to true so I do not believe that this is the issue.

Any other ideas on what the issue could be?

Kevin

Answer 4

Hi,

I worked out what was going on.

I have an obfuscator which is hidden away in the .vbproj file.

This should have been set on only for compiling release code but was it was turned on for both Release and Debug.

I turned it off for Debug and it sorted the issue.

Kevin

Answer 5

Hi Kevin,

Glad the issue has been resolved and thank you for sharing the solution with us!

Have a nice day:)

 

Best regards,

Fletcher

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].