Inventor API - Visual Studio Debug - Binding Errors on Start

[NateLFO]

I posted this on Reddit r/AutodeskInventor, but I figured I'd post it here as well since r/AutodeskInventor is a general Inventor sub and this forum is dedicated to Inventor scripting.

I am just getting started with using Visual Studio for Inventor API (VB code) and while I do have my first add-in running (through the debug start), I did notice that there are a lot of binding errors that appear in the debug immediate window as Inventor launches. The add-in works just fine, and I don't get any actual error messages, I'm just curious if this is normal, if I have something setup wrong, or what.

I've been following the KetivAVA tutorials for getting started with Visual Studio and Creating Basic Geometry: Inventor API to do this. I am using Inventor 2022 and Visual Studio 2022. This particular add-in that I'm testing is a simple one to create a circle on a sketch and extrude it. It uses a form for setting the radius, X and Y coordinates, and the extrusion length.

The messages that appear are a bunch of System.WIndows.Data Errors for WIndows Control, dealing with toolbar gradients, RelativeSource FindAncestor, Windows.Controls.ItemsControl Ancestor horizontal and vertical alignment, QuickAccess Undo Button and Redo Button, theme visibility, canvas, margins, and content presenter binding issues. Everything looks fine and works fine when I test it out through the debug, I'm just wondering why I'm getting all of these messages. It appears that these all have to do with the form. I can post the actual text, but it's a lot of them, 77 faults in total, 48 when I look at the XAML Binding Failures tab.

Just for the heck of it, because I wasn't sure if it was necessary, I did change the "Copy to Output Directory" option for the form to Copy if Newer, like I have for the add-in and it made no difference.  By the way, I did change the debug output to the Inventor Addins folder, so it's not going to the default Visual Studio location. 

Any help you can provide would be greatly appreciated. 

[nmunro · Accepted solution]

If you examine the exceptions a bit more closely you will see that they are all happening in Inventor dlls which are completely out of your control. No need to worry about them unless you see something with your add-in name in the exception. Even then unless it causes an issue you can generally ignore them.

[NateLFO]

Ok, thanks. I just wanted to make sure that I wasn’t missing something, or had something setup incorrectly.