The .pdb debug symbol files generated by Visual Studio contain a unique hash that must match the corresponding .dll or .exe. Which means they must come from the same build. Identical inputs (source code, compile flags, link flags) are not sufficient, the .dll, .exe or .xlls must be from the same actual build. Since Visual Studio generated the .pdbs it should know where to find them.
An alternate approach to that outlined in the link you gave is to set excel.exe as the launch command for the debug session in the project that builds the .xll. Look in project properties, Debugging/Command. That way you can launch the whole debug session from inside VS, instead of launching excel from outside, then attaching to an already running process.
Good luck!
Cheers
John
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org!
http://sdm.link/slashdot_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users