Latest Contributions by DanielRouleau

我想适应EditingTemplates CreateTemplateWithCIM sample to write a template in which I have specified a default construction tool, and want to set some tool options on this custom construction tool. What I am seeing is that, despite trying a number of different ways to do so, the tool options are never persisted into the template using CIM. The tool options collection is always null when the construction tool is constructed. Setting the tool options using the Manage Template dialog works fine and everything works there. I tried this originally with Pro 2.9 and then adapted the sample to Pro 3.0 and still am not having luck. Any tips on getting these tool options to save with the newly created template using CIM? Here is the relevant chunk of code that I've tried adapting. //get the CIM layer definition var layerDef = layer.GetDefinition() as CIMFeatureLayer; //set new template values var myTemplateDef = new CIMRowTemplate(); myTemplateDef.Name = "Daniel Template With Construction"; myTemplateDef.Description = "some description"; // set the default construction tool to our custom tool myTemplateDef.SetDefaultToolID("EditingTemplates_Tools_ConstructFacilitiesTool"); myTemplateDef.AllowToolID("EditingTemplates_Tools_ConstructFacilitiesTool"); // Add default tool options for this construction tool var toolOptions = new Dictionary(); toolOptions.Add("CustomSubtype", "MySubtypeCode"); myTemplateDef.ToolOptions = new[] { new CIMEditingTemplateToolOptions() { //ToolProgID = "EditingTemplate_Tools_ConstructFacilitiesTool", I tried this to no avail ToolProgID = "cdf8db34-6880-4e16-8253-145d739de379", // id from daml Options = toolOptions, } }; var layerTemplates = layerDef.FeatureTemplates?.ToList(); if (layerTemplates == null) layerTemplates = new List(); //add the new template to the layer template list layerTemplates.Add(myTemplateDef); //update the layerdefinition with the templates layerDef.FeatureTemplates = layerTemplates.ToArray(); // check the AutoGenerateFeatureTemplates flag, // set to false so our changes will stick if (layerDef.AutoGenerateFeatureTemplates) layerDef.AutoGenerateFeatureTemplates = false; //and commit layer.SetDefinition(layerDef); ... View more

Hello, I have been reliably using the steps outlined in the following help doc to sign our ArcGIS Pro Add-Ins with no problems, until recently. https://github.com/esri/arcgis-pro-sdk/wiki/ProGuide-Digitally-signed-add-ins-and-configurations Lately, when attempting to run ArcGISSignAddIn.exe with the parameters suggested, I am getting a failure because a dialog is attempting to display and I am running headless in an Azure DevOps build pipeline. The version of Pro I'm using is 2.3.2, has there been any change in how this tool is working that would explain the behavior? Exception I get is copied below but not super informative as it doesn't display what the dialog was attempting to tell me. I can't pinpoint at exactly which release this stopped working but I see several builds that successfully signed the end of last year on Pro 2.2. Unhandled Exception: System.InvalidOperationException: Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application. at System.Windows.Forms.MessageBox.ShowCore(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options, Boolean showHelp) at ArcGISSignAddIn.SignAddInHandler.OutputMsg(String msg) at ArcGISSignAddIn.SignAddInHandler.CommandLineSignAddIn(String[] args) at main(String[] args) ... View more

I have a conundrum with versioned editing when a user has finished their work and edits are outstanding. Checking the state 'esri_editing_HasEdits' is easy and sufficient for determining when there are edits, but I need to call the Save Edits button 'esri_editing_SaveEditsBtn' to prompt the user to save or discard the edits, in lieu of there being any SDK call that I have found to support interacting with the Editor. The challenge comes in using IPluginWrapper to get an ICommand to execute, as there is no way to wait (or await) the result of the dialog that is inevitably presented to the user. This means I cannot tie any further necessary operations conditionally after the call to Save Edits, because the Execute command returns immediately before the user has had a chance to interact with the dialog. Is there any other way to accomplish what I am attempting, or perhaps any plans to surface this sort of editing control via the SDK? ... View more