Latest Contributions by RichardDaniels

If you have a ArcGIS Developer Subscription or access to My.esri.com via a Subscription (and our Primary ESRI contact enabled it) you should be able to click the Download button and download the MIS, ISO, etc. file. There is an option or order an actual thumb drive with the installers as well, but you have to Request this, it is no longer sent automatically to ESRI customers. ... View more

you may be looking for C:\Program Files\ArcGIS\Pro\Resources\ProjectTemplates ... View more

Suggest you place the code on a network share drive, thus you don't have to deploy the python code to every machine. Then the path would be \\myserver\mypythongcode\thecode.py ... View more

Here is the message from ArcGIS Pro 3.1.1 which references Microsoft.NETCore.App   ... View more

ArcGIS Pro 3.1 requires 6.0.5 or Higher. We installed Windows Desktop Runtime 6.0.x (was 13 now 16) which does not work and is. We have also tried the pure Microsoft .Net Runtime (x64) which does not resolve the issue. Recall, most end users do not have permissions to Install .Net Framework themselves. Your documentation needs to use the Exact given the wide array of options at Download .NET 6.0 (Linux, macOS, and Windows) (microsoft.com)<>. ... View more

Sounds like you are using some internal project bar related to the tool you are running, vs. one you wrote yourself. When you need full control of the bar use a System.Windows.Forms.ProgressBar on a WinForm . For example, here I'm loading a database into memory within an ArcGIS Pro addin. [cid:[email protected]] Code behind looks similar to this. private Form myProgressBar; public void LoadDatabase (SqlDataReader theDataSource) { if (myProgressBar==null) { myProgressBar = new wsdotCode.frmProgress(); } System.Windows.Forms.ProgressBar pbar; pbar = myProgressBar.Controls.Find("progressBar1", true).FirstOrDefault() as System.Windows.Forms.ProgressBar; pbar.Value = 0; myProgressBar.Show(); //increment the progress bar and read data While not EOF(theDataSource) { LoadRow(theDataSource) progressUpdate(pbar); } myProgressBar.Close(); } private void progressUpdate(System.Windows.Forms.ProgressBar myBar) { //step size is set in the designer myBar.PerformStep(); myBar.Refresh(); myBar.Parent.Refresh(); if (myBar.Value >= 100) { System.Threading.Thread.Sleep(200); } else { System.Threading.Thread.Sleep(100); } } ... View more

An add-in built to run under ArcGIS Pro does require the targeted desktop software to be loaded on the build machine. Since the software never 'starts' on the build machine you would never need to point it to a license server, single use license, or ArcGIS online organization named user account. If Pro is started it would open to the 'licensing' screen and give you an opportunity to enter credentials or the license server name. Thus you can actually validate that the installer 'worked' without a license as well. ... View more

The aptx file is usually loaded into the Pro as a projec, use the layout template for a map layout. You can use code to use the 'current active map' as the primary may shown in the newly created layout template. Recall templates can have 'tags' for text items, this means you can search for them an replace the text as well (e.g., in this example we have map layout template with Title1, subtitle1, Title2, subtitle2, etc. tags that get populated form a form) prior to executing the LoadLayoutTemplate sub. internal static void LoadLayoutTemplate(string myMapTemplatePath, string lytTitle1, string lytTitle2, string lytSubTitle1, string lytSubTitle2, string lytDateInfo, string lytDataSource, Map lytMap, Envelope lytEnvelope) { // Load WSDOT Layout templates, added as a Tool at ArcGIS Pro 2.9. try { IProjectItem myItem = ItemFactory.Instance.Create(@myMapTemplatePath, ItemFactory.ItemType.PathItem) as IProjectItem; IProjectMultiItem myMultiItem = myItem as IProjectMultiItem; LoadNewLayoutItem(myMultiItem, lytTitle1, lytTitle2, lytSubTitle1, lytSubTitle2, lytDateInfo, lytDataSource, lytMap, lytEnvelope); } catch (Exception eX) { ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("Unable to Load requested Layout template ( internal static void LoadLayoutTemplate(string myMapTemplatePath, string lytTitle1, string lytTitle2, string lytSubTitle1, string lytSubTitle2, string lytDateInfo, string lytDataSource, Map lytMap, Envelope lytEnvelope) { // Load WSDOT Layout templates, added as a Tool at ArcGIS Pro 2.6. try { IProjectItem myItem = ItemFactory.Instance.Create(@myMapTemplatePath, ItemFactory.ItemType.PathItem) as IProjectItem; IProjectMultiItem myMultiItem = myItem as IProjectMultiItem; LoadNewLayoutItem(myMultiItem, lytTitle1, lytTitle2, lytSubTitle1, lytSubTitle2, lytDateInfo, lytDataSource, lytMap, lytEnvelope); } catch (Exception eX) { ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("Unable to Load requested Layout template (pagx). " + eX.ToString(),"Information",0); } } public async static void LoadNewLayoutItem(IProjectMultiItem theItem, string lytTitle1, string lytTitle2, string lytSubTitle1, string lytSubTitle2, string lytDateInfo, string lytDataSource, Map lytMap, Envelope lytEnvelope) { //add the newly project item to the current project; must be public to avoid threading errors! try { //add the layout to the project and wait for import to complete await QueuedTask.Run(() => Project.Current.ImportItem(theItem, true)); //wait 1 econdto ensure we are Ready await Task.Delay(1000); // Reference the new active layout in the project LayoutView lytView = LayoutView.Active; if (lytView != null) { await QueuedTask.Run(() => { Layout myLayout = lytView.Layout; // set the text elements based on values passed from frmLayouts // help at https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/index.html#topic11176.html // https://github.com/Esri/arcgis-pro-sdk/blob/master/Examples/Layouts/MethodSnippets.cs TextElement txtTitles = myLayout.FindElement("Title1") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytTitle1, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("Title2") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytTitle2, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("SubTitle1") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytSubTitle1, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("SubTitle2") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytSubTitle2, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("DateInfo") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytDateInfo, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("DataSource") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytDataSource, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } MapFrame frameMap = myLayout.FindElement("Layers Map Frame") as MapFrame; if (frameMap != null) { //Update the MapFrame to use the Map that was active when the tool was run; set layout map element envelope based on the active map (added 1/28/2022) if (lytMap != null) { frameMap.SetMap(lytMap); frameMap.SetCamera(lytEnvelope); } } }); } } catch (Exception eX) { //do nothing ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("System Error: " + eX.ToString(), "Error",0); } } ). " + eX.ToString(),"Information",0); } } public async static void LoadNewLayoutItem(IProjectMultiItem theItem, string lytTitle1, string lytTitle2, string lytSubTitle1, string lytSubTitle2, string lytDateInfo, string lytDataSource, Map lytMap, Envelope lytEnvelope) { //add the newly project item to the current project; must be public to avoid threading errors! try { //add the layout to the project and wait for import to complete await QueuedTask.Run(() => Project.Current.ImportItem(theItem, true)); //wait 1 econdto ensure we are Ready await Task.Delay(1000); // Reference the new active layout in the project LayoutView lytView = LayoutView.Active; if (lytView != null) { await QueuedTask.Run(() => { Layout myLayout = lytView.Layout; // set the text elements based on values passed from frmLayouts // help at https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/index.html#topic11176.html // https://github.com/Esri/arcgis-pro-sdk/blob/master/Examples/Layouts/MethodSnippets.cs TextElement txtTitles = myLayout.FindElement("Title1") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytTitle1, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("Title2") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytTitle2, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("SubTitle1") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytSubTitle1, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("SubTitle2") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytSubTitle2, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("DateInfo") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytDateInfo, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } txtTitles = myLayout.FindElement("DataSource") as TextElement; if (txtTitles != null) { TextProperties txtProp = new TextProperties(lytDataSource, txtTitles.TextProperties.Font, txtTitles.TextProperties.FontSize, txtTitles.TextProperties.FontStyle); txtTitles.SetTextProperties(txtProp); } MapFrame frameMap = myLayout.FindElement("Layers Map Frame") as MapFrame; if (frameMap != null) { //Update the MapFrame to use the Map that was active when the tool was run; set layout map element envelope based on the active map (added 1/28/2022) if (lytMap != null) { frameMap.SetMap(lytMap); frameMap.SetCamera(lytEnvelope); } } }); } } catch (Exception eX) { //do nothing ArcGIS.Desktop.Framework.Dialogs.MessageBox.Show("System Error: " + eX.ToString(), "Error",0); } } ... View more

The desktopVersion is the lowest Pro version you would like to support in your Add-In. ... View more

All 2.0 add-ins will load in any 2.x version of ArcGIS Pro so you don't have to rebuild the Add-In for every release. Version 3.0 is a breaking change and will require refactoring since it uses .Net 6 vs. Framework .Net 4.8. Key controlling factor is the settings in our config.daml file. The version number shown should always be 2.0 for Add-Ins for that major release.    <ArcGIS defaultAssembly="BasicMapTool2.dll" defaultNamespace="BasicMapTool2" xmlns="http://schemas.esri.com/DADF/Registry" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.esri.com/DADF/Registry file:///C:/Program%20Files/ArcGIS/Pro/bin/ArcGIS.Desktop.Framework.xsd"> <AddInInfo id="{aa226987-8efd-4d34-b606-3e731c8cd2ff}" version="2.0" desktopVersion="2.9.0"> <Name>MapCoordinatesTool</Name>   After I updated this to run under ArcGIS Pro 3.x the second line became: <AddInInfo id="{aa226987-8efd-4d34-b606-3e731c8cd2ff}" version="3.0" desktopVersion="3.0.3.36057"> ... View more

You had asked about clearing the graphics layer on closing the tool. I use a clearGraphics() overlay function that is called when the user clicks the Close button on the form Or changes to another tool.  You can catch the Deactivate event by adding this code in your primary namespace (i.e., the same module where you will find the OnToolActivateAsync() procedure).   protected override Task OnToolDeactivateAsync(bool hasMapViewChanged) { clearGraphics(); return base.OnToolDeactivateAsync(hasMapViewChanged); }   ... View more