Breakpoint...Binary not built with debug information.

[Andrew DeBear]

"Breakpoint will not be hit...Binary not built with debug information."

A couple of years ago, I made an Excel Add-In with Visual Studio 2021 and ExcelDNA 1.1 (I think). Everything was debugging and compiling fine.

I've recently upgraded to Visual Studio 2022 and ExcelDNA 1.6.0.

It's compiling and the UDFs appear to be working in Excel, but when debugging the code, it's ignoring breakpoints.

The Breakpoints manager indicates that "This breakpoint will not currently be hit. No symbols have been loaded for this document."

And in the Modules list, for the XLL that was created, it says the symbol status is "Binary was not built with debug information."

When I look in the [project]\bin\Debug folder, a [project].pdb has been created.

Any suggestions for how to get the breakpoints working in VS?

Thanks.

[Sergey Zhilyakov]

Hi,

The Breakpoints manager indicates that "This breakpoint will not currently be hit. No symbols have been loaded for this document."

Check the properties of the project and make sure the following checkbox is deactivated.

Best regards,

Sergey

--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/473ac5c7-c174-47fb-aee0-0eb72398c9d1n%40googlegroups.com.

[Andrew DeBear]

Thanks for the reply, Sergey, but no dice.

I found this thread on stackoverflow. And I think I tried all of the recommended solutions, but nothing worked for me. 

https://stackoverflow.com/questions/2155930/how-do-i-remedy-the-breakpoint-will-not-currently-be-hit-no-symbols-have-been?rq=1

So I backed up the code files and deleted my whole solution. 

I tried starting a new project from a template. and initially set it up for .net Framework 4.8 and used ExcelDNA 1.6, but I kept running into a weird error about a "...64.XLL was not being created".

So I scrapped that project and tried a new one for .net Framework 4.7.x and used Excel DNA 1.5.1...everything worked fine.  ¯\_(ツ)_/¯

I really need to start drinking again.