Replies: 2 comments 14 replies
|
Turns out that yes, my dependency was up to date for this plugin, not another. So updating that fixed the issue, but i shouldn't have to do that. |
0 replies
|
To make sure I understand, your complaint is that when you evaluate the property it fails with |
14 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Made a change to one of my dependencies, adding a property, rebuilt every parts of this C# plugin of mine.
Yet, for some reasons, The debugger refuses to either let me view the value directly, place a condition breakpoint, or a logpoint.
Since this is a plugin, and not a standalone program, I'm remote debugging the Managing app, which loads my plugin.
The PDB files are up to date & the dlls are up to date, as the plugin runs without issues.
Decompilation shows the presence of the property & even the debugger itself shows the property when the containing object is added to watch.
What are the others steps that i should take to make it work normally again?
All reactions