web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

I seem to be missing pdb files for Dexterity/SDK...

(0) ShareShare
ReportReport
Posted on by

Hello all,

Full disclosure: Totally winging it here :)

Making lots of progress in writing my first addin dll...

Got VS2017 everything runs smoothly and all, but when in debug mode I can not access Dexterity variables, need those pdb files...

I can continue by spitting out to a string the variable I want to see and all that, but getting my debugger fully working would be great.

Looked around for those files, locally and online, to no avail. 

This might be too vague, but as I said I am totally winging it, so any extra information needed I can provide it, when I find it :)

Makes sense to post this: 

Microsoft.Dexterity.Bridge.dll and Application.Dynamics.dll

Runtime Version: v4.0.30319

Version: 16.0.0.0

Pretty sure my installation of all this was "not proper", but I somehow got everything running...

Thank you,

~S

*This post is locked for comments

I have the same question (0)
  • Patrick Roth Profile Picture
    on at

    You can't access what "Dexterity variables"?  Do you mean GP Global Variables?

    You won't find any Dexterity PDB files anywhere (Dynamics.pdb for example)- but those would be the symbols of the runtime engine and not what you would find useful anyway.

    Unless you mean YOUR pdb files for your addin.

    When you build your dll, you should always make sure to build in Debug mode and that you debug with YOUR symbols loaded.  I typically copy the dll & the pdb into my GP\addins folder when I debug my addin.

  • Community Member Profile Picture
    on at

    First off, I switched the project to an e-connect solution, so that's done.

    But to further my understanding here :)

    I was doing that, the Debug mode and everything in my addins folder and all usual debug things were working... breakpoints and all that.

    But once a breakpoint was hit I could watch variables I made, but anything dexterity based was not showing on my watch window and giving missing .pdb file error.

    To circumvent this I was using an object dumper class to dump those variables into an object I declared and then watch that one...

    Never found out if I would find anything useful in those objects, since as I mentioned I switched everything over to e-connect, but for future reference I was/am still interested into what I was doing wrong... The answer could be "nothing really, the object dumping is the only way to get a look inside those variables, because there is nothing of use in there anyways"...

    Just since I was/am winging this, looking under the hood of everything "works faster for me" in a crunch than learning the whole SDK proper ways...

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans