Latest Contributions by RichardDaniels

Prior to ArcGIS Pro 3.2, you had to update the License Manager to the version released with Pro, e.g, 2022.0 was ArcGIS Pro 3.0 and 2022.1 was for ArcGIS Pro 3.1. For some reason, ArcGIS Pro 3.2 works with both LM 2022.1 and LM 2023.0. ... View more

There are two registry options to consider, one is per machine and the other is per user. Per user is looked at FIRST, then if not found the per machine version of the key is looked at. These keys are at : HKEY_CURRENT_USER\SOFTWARE\ESRI\ArcGISPro\Licensing HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing The value of the LICENSE_SERVER key looks like @my_ESRILIC;@MY_ESRILICBACKUP. Technically you can have a port number before the @ symbol, but in ArcGIS Pro this does not appear to be honored (unlike ArcMap where the port number is usually set between 27000 and 27009). Of note, the @ symbol is added automatically by ArcGIS Pro when you edit the License Manager names (or BACKUP name). This means you may end up with @@MY_ESRILIC in the registry when entering the LICENSE_SERVER name via the ArcGIS Pro License Settings page. When testing, recall that the connection test is done during ArcGIS Pro start-up, this means by the time you get to the Licensing screen the connection check is already completed. This means any changes made  to the registry manually or via the ArcGIS Pro interface are not 'operational' until ArcGIS Pro is restarted. ... View more

Found HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing\LICENSE_SERVER key, will give that a try. ... View more

Thank you, this solution still works with ArcGIS Pro 3.1. The app mentioned updates Computer\HKEY_CURRENT_USER\SOFTWARE\ESRI\ArcGISPro\Licensing or Computer\HKEY_CURRENT_USER\SOFTWARE\ESRI\ArcGISPro\Licensing\Extensions prior to the user clicking the 'Go Pro' button. This list of extensions is just an array of extensions that are owned by our agency'.  The known good ESRI extensions names to use within the registry in the .\Extensions area include:           // Sets up the list of extensions             string[] extList = { "3D Analyst Pro", "Spatial Analyst Pro", "Network Analyst Pro", "Data Interoperability Pro", "Data Reviewer Pro", "Workflow Manager Pro", "JTX Pro", "Aviation Airports", "Location Referencing Pro", "Production Mapping" };            ... View more

If you have not done an Add-In before, spend a few minutes to understand how the projected is wired together. As a start look at the config.daml file and understand what the XML tags mean. One key, is everytime you rebuild the Add-In for debug you need to updated the <Date> tag to a newer date/time, otherwise ArcGIS Pro will not reload the code. Second is that in the <modules> section you define a Module ID, usually in the <insertModule id> tag, this has our className  value that is used to connect the interface (partially designed in the config.daml) to your underlying code. For example, if your className="LoadMyToolCode" then you would need a LoadMyToolCode.cs file in your solution. This cs file usually only has 53 lines since its entire purpose is to load and launch your code module when the button defined in the Config.xml is clicked in ArcGIS Pro.  ... View more

The answer depends on what you want to do with the data. The reply by  GintautasKmieliauskas creates a data source for immedate use with a GP processing. However, if you are just reading a text file into an array to concatenate data, as you mention in your post, you can do it all with standard C# coding. This could be done with the basic old readline, writeline of C or in a modern way using the DataTable data type. If reading from a SQL database table vs. ascii flie suggest using System.Data.SqlClient methods. Simple example at .net - How to read SQL Table data into a C# DataTable - Stack Overflow. ... View more

If you are using Visual Studio 2022 to build your ArcGIS Pro 3.x package and include a reference to a NuGet packet as a resource you can have problems. If you install the NuGet package on your computer and then reference the DLLs on disk the NuGet references will work. However, if you reference (i.e., add) and NuGet package itself (in Visual Studio), you will receive an XAML error showing, "Error: Could not load file or assembly 'ArcGIS.Desktop.Framework, Culture=neutral' or one of its dependencies at compile time. After upgrading a 2.x add-in to 3.x in Visual Studio check your .csproj file. Recommendation on another post is to removing the False attribute for each DLL in the csproj file. (see Solved: Re: Extensions NuGet package not loading in VS 202... - Esri Community<>).   Note - I first ran across this issue when trying to convert my ArcGIS Pro 2.9 (Visual Studio 2019) project to use new webview2 control in Visual Studio 2022. The solution was to search for webview2 in NuGet, and then install it. You install the Microsoft.Web.WebView2 SDK NuGet package for into the current project.  ... View more

Also, with .Net 6 there is a breaking change. Breaking change: System.Drawing.Common only supported on Windows - .NET | Microsoft Learn. In short, .Net Core does not include System.Drawing.Common but .Net Framework does. ... View more

Are you sure it is possible to modify buttons on a drop down menu? In some cases the buttons are not directly controlled by a user editable DAML file. See: is it possible to add button on toolbar in attribu... - Esri Community ... View more

At .Net 6.0 System.Drawing.Common is not as common as you may think. Ensure Miorosoft .Net Runtime and Microsoft .Net Desktop Runtime are installed on the build machine. Current version is 6.0.21. ... View more

Since the Add-in is compiled code, e.g., C#, you can reference the application properties with Project.SetProperty and Project.GetEvaluatedProperty(String) Method. Use these rather than config.daml to hold application and user properties specific to the add-in (a.k.a., visual studio project). Since you can reference any location in any file location, recommend using a shared UNC path like \\mydomainserver\mygisfolder\mycustomappfolder<> and store the shared files there. That way you only have one copy for your entire agency. ... View more

To try to find out what is happening you may want to add this to the task that you want to await, If you place a try/catch block around the ENTIRE body of your event handler, then you can prevent any exceptions from bubbling up across that async void boundary. try { await SomeTaskYouWantToAwait(); } catch (Exception ex) { // TODO: put your exception handling stuff here Console.WriteLine($"[TryAsync Error Callback] Our exception handler caught: {ex}")); } ... View more