Latest Contributions by Wolf

The ArcGIS Pro SDK community samples repo contains an example of two Add-ins interfacing.  Under the Framework folder you'll find AddInOne and AddInTwo and the shared component AddInShared. If you have a reusable versioned class library, you'll have to sign the add-in (and library) as @SelimDissem  said above. If you just want to 'share' common source code between your two Add-ins you can also add a reference to your 'shared' CS source code as shown here (in which case, you don't need to worry about DLL versions):   ... View more

What is the 'other part' of your add-in doing ?   ... View more

Your approach to move your source code to a previous release version of ArcGIS Pro is correct: You have to move the source code to a development machine with ArcGIS Pro 3.1 installed. You also have to install the matching ArcGIS Pro SDK (3.1 in your case) Visual Studio extensions. You open your Add-in solution in Visual Studio and change the project's 'Target Framework' back to .NET 6.0, clean the project, and then rebuild the project. Use the ArcGIS Pro SDK's 'Pro Fix References' tool (right click on the solution or project file) if the reference path to ArcGIS Pro assemblies changed. It is possible that you get errors when you rebuild the add-in.  Errors can be caused by functionality added by .NET 8.0 (in my test i noticed that the '[]' collection expression is not valid in .NET 6.0) and errors can be caused by functionality added by an ArcGIS Pro release.  In my test (i downgraded from 3.5 to 3.2) and i didn't get any errors by non-existing functions or assemblies of ArcGIS Pro 3.2.  But you can get errors (like your "KnowledgeGraph" depended assembly that were caused by additions to future ArcGIS Pro releases. Once your Add-in builds under the older ArcGIS Pro release you have to update the desktopVersion attribute in the config.daml file to reflect the minimum required version you want your add-in to work with.   See here:  ProConcepts Advanced Topics · Esri/arcgis-pro-sdk Wiki "Add-ins and configurations are forwards compatible across all minor versions of ArcGIS Pro. Add-ins and configurations are not forward compatible across major versions (eg 2.x, 3.x, etc). Add-ins and configurations are not backwards compatible across any versions of ArcGIS Pro." Regarding the changes in each release can find the 'What's new' for all editions here: Home · Esri/arcgis-pro-sdk Wiki     ... View more

You didn't share your tool's OnSketchComplete method.  Is it possible that it contains code to create an annotation feature?   If you create a Construction Tool from the ArcGIS Pro SDK item templates you notice that this code is inserted with the template: // Create an edit operation var createOperation = new EditOperation(); createOperation.Name = string.Format("Create {0}", CurrentTemplate.Layer.Name); createOperation.SelectNewFeatures = true; // Queue feature creation createOperation.Create(CurrentTemplate, geometry); // Execute the operation return createOperation.ExecuteAsync(); this snippet will actually create an annotation feature using the current template (which usually has the string 'Text' as the default value): My guess is that only a 'Create' call on an EditOperation that is using the current template will produce your 'Text' annotation entry.  Also, if you get the text for the annotation feature from a Query Cursor make sure to 'copy' the text string when you retrieve the string from your current feature.  I would do the same if you get the geometry via a feature cursor, make sure to .Clone() the geometry. ... View more

The 'Text' string you're seeing is coming from the annotation editing template.  Somehow, there must be an extra 'createOperation.Create' function call that adds the default template settings to the annotation feature class.  I wrote a sample add-in which is an annotation tool that allows you to select a set of point features (cities in my sample) via rectangular selection and then creates annotation features for all selected point features. I attached the sample code and also the project file i used for testing.  Maybe you can compare the sample code to your code and find the difference.   I tested my addin in both 3.4 and 3.5. To use the sample, open the attached SampleAnno.aprx, use the Create Features dockpane to select the 'Retrofit Annotation for points' tool and rubber band select a few cities to create the matching annotation strings. ... View more

I tried this Addin using ArcGIS Pro 3.4 and i see the .lock files in 3.4 as well.   As far as i can tell, the geodatabase connection must still be open.   I think the same happens when you use the Catalog dockpane and manually open the Geodatabase:  a .lock file is created and stays until you close Pro.  I don't see a change in behavior between 3.4 and 3.5.    ... View more

I made a small sample add-in that imports a csv (included as add-in content) and adds the data into a new feature class in your project's default geodatabase.   To run the add-in start with a new [empty] map [template] and open the 'FGB Importer' tab.  Click the 'Show FGB Importer' button to open the Importer dockpane.  On the dockpane all paths etc. should be filled in.  Just click the 'Import into F/C' button.  This will create a new feature class in the given geodatabase and then adds the csv data to that feature class.  Maybe i left out something in my code, but i also have the remaining .lock file in my geodatabase folder.  I am currently running 3.6 but i will try 3.4 tomorrow. I will add this code to the community samples with the 3.6 release, it hasn't been fully debugged. ... View more

I am still looking at this, but this appears to be a bug in the API since the Path property is null when the tool is being executed.  It looks like when the event is triggered only the GPResult property is populated in GPExecuteToolEventArgs , but unfortunately GPResult doesn't contain the tool path or id either.  It looks like the Event is called twice, once with IsStarting set to 'true' before the tool runs and once with IsStarting set to 'false' after the tool completes.  There are no provisions to 'cancel' the tool, so once the Path property is set to a proper value you will be able to get the tool's name to display a warning in case a 'specific' tool is run.  I will report the issue to the GeoPrcoessing dev team.   The 3.5 release contains a new GeoProcessing community sample called 'GPToolInspector' that contains the code to retrieve GPTool attributes from a given path.  The 3.5 release is available next week.  But unfortunately, you'll have to wait for the 'Path' property fix before you can implement a warning. ... View more

I am looking at this issue, but in the meantime i think you can just use the button directly instead of setting the set enable editing API method: // if not editing if (!Project.Current.IsEditingEnabled) { var res = MessageBox.Show("You must enable editing to use editing tools. Would you like to enable editing?", "Enable Editing?", System.Windows.MessageBoxButton.YesNoCancel); if (res == System.Windows.MessageBoxResult.No || res == System.Windows.MessageBoxResult.Cancel) { return; } // Project.Current.SetIsEditingEnabledAsync(true); // use the esri_editing_ToggleEditingBtn instead for .SetIsEditingEnabledAsync var damlId = "esri_editing_ToggleEditingBtn"; IPlugInWrapper wrapper = FrameworkApplication.GetPlugInWrapper(damlId); var command = wrapper as ICommand; if ((command != null) && command.CanExecute(null)) command.Execute(null); } ... View more

I attached a small sample add-in project that has a Combo dropdown on the ArcGIS Pro ribbon and two dropdowns on a Dockpane.  I am using a dictionary (keys and values) to 'feed' the dropdown content. ... View more

Uma wrote a sample with a tree control that might help you out.  arcgis-pro-sdk-community-samples/Editing/EditorInspectorUI at master · Esri/arcgis-pro-sdk-community-samples Did you try to emulate the dropdown selection options as it is shown on the Attribute editing dockpane as shown on the screenshot below?  I will try to provide a sample implementation in the upcoming 3.5 release for the community samples.     ... View more

I am not sure if this will help you, but it seems to me that you can add code in your tool to deal with the hidden/visible state of your dockpane.  for example: protected override Task<bool> OnSketchCompleteAsync(Geometry geometry) { // in order to find a dockpane you need to know it's DAML id var pane = FrameworkApplication.DockPaneManager.Find("your_dockpane_id_here"); // determine visibility bool visible = pane.IsVisible; MessageBox.Show($"Dockpane is {(visible ? "visible" : "not visible")}", "Dockpane Visibility"); if (!visible) pane.Activate(true); return base.OnSketchCompleteAsync(geometry); } ... View more

@mstranovsky  Your code snippet is not applicable in an ArcGIS Pro Add-in.  There are two patterns in ArcGIS Pro to deploy a ComboBox: 1)   If you are using a Pro Combo box ribbon control you would load the 'Ribbon' Dropdown from a dictionary like this: internal class TestComboBox : ComboBox { private bool _isInitialized; /// <summary> /// Combo Box constructor /// </summary> public TestComboBox() { UpdateCombo(); } // create a dictionary with an entry for each US state, the value should be the capital city of that state private Dictionary<string, string> _stateCapitals = new Dictionary<string, string> { { "Alabama", "Montgomery" }, { "Alaska", "Juneau" }, { "Arizona", "Phoenix" }, { "Arkansas", "Little Rock" }, { "California", "Sacramento" }, { "Colorado", "Denver" }, { "Connecticut", "Hartford" }, { "Delaware", "Dover" }, { "Florida", "Tallahassee" }, { "Georgia", "Atlanta" } }; /// <summary> /// Updates the combo box with all the capitals of the US states /// </summary> private void UpdateCombo() { if (_isInitialized) SelectedItem = ItemCollection.FirstOrDefault(); if (!_isInitialized) { // Updates the combo box with all the capital names of the US states foreach (var capital in _stateCapitals.Values) { Add(new ComboBoxItem(capital)); } _isInitialized = true; } Enabled = true; SelectedItem = ItemCollection.FirstOrDefault(); } /// <summary> /// The on comboBox selection change event. /// </summary> /// <param name="item">The newly selected combo box item</param> protected override void OnSelectionChange(ComboBoxItem item) { if (item == null) return; if (string.IsNullOrEmpty(item.Text)) return; } } 2. If you are using a combobox on a Dockpane, you should use the MVVM pattern to populate the combobox content.  In this case, please model your code after @SumitMishra_016 's sample snippet. ... View more