Select to view content in your preferred language

ArcGIS Pro Crashing During Debug When Accessing Feature Class Via GUI

210
1
Jump to solution
4 weeks ago
JoePolaski
Emerging Contributor

Hi all,

I have been experiencing a very strange issue that, I initially assumed was a bug in my Add-In I am developing. However, after some testing and narrowing down what causes it, I have been able to recreate the issue in a brand new out-of-the-box add-in project with that being the only add-in installed.

The Problem:

I have ArcGIS Pro SDK 3.3 installed in Visual Studio 2022, as well as ArcGIS Pro 3.3 installed on my computer with a valid named user license. If I create a brand new add-in project and go to run it in debug mode, making sure it is the only add-in currently installed in pro, then I go into the project and create a feature class in the project database and drag it into my map, if I right click on the feature class in the contents pane, pro immediately throws an exception. Similarly, if is start the same way and then right click the feature class in catalog pane and select open table, it again throws an exception.

The Exception:

System.NullReferenceException: 'Object reference not set to an instance of an object.'

The debugger raises this exception on line 1567 of ArcGIS.Desktop.Editing.Settings class in the getter of the Property public bool TableOptionsUriSchemesSupported. 


If I go and look in the watcher under local variables I can also see that the same exception is being raised for the following properties.

TableOptionsDisableAddRow
TableOptionsFontSize
TableOptionsUriFilesSupported

Has anyone experienced this before or have an idea of why these properties are null? Again this is in a brand new add-in project with nothing added to it at all yet just the basic out of the box project. It happens during debug mode only. If I run pro normally these feature work fine, seemingly regardless of what add-ins are installed. I appreciate any advice or help anyone can provide. Thanks!

 

0 Kudos
1 Solution

Accepted Solutions
JoePolaski
Emerging Contributor

Hopefully someone sees this and learns from my mistake. The problem was that I had "Enable Just My Code" unchecked in my debugger options. While this can be helpful in certain cases for deep diving into issues, I wouldn't recommend forgetting you left it unchecked like I just did.

View solution in original post

1 Reply
JoePolaski
Emerging Contributor

Hopefully someone sees this and learns from my mistake. The problem was that I had "Enable Just My Code" unchecked in my debugger options. While this can be helpful in certain cases for deep diving into issues, I wouldn't recommend forgetting you left it unchecked like I just did.