Latest Contributions by RichardDaniels

Also, if you setup your test environment as described above, but it looks like 'the old code' keeps running, remember to CLEAR your Cache at C:\Users\<UserName>\AppData\Local\ESRI\ArcGISPro\AssemblyCache ... View more

Since you are talking about Development in Visual Studio, it sounds like you need to setup your debug environment to launch and run ArcGIS Pro. Using the debug environment gives you the ability to do 'hot reload' of code so you can edit 'most' forms and modules without restarting ArcGIS Pro, secondly recall that you need to update the config.daml <Date>02/04/2025 10:45:00 AM</Date> tag every time you rebuild and deploy your add-in. In Visual Studio you need to setup you test environment. In your .\properties folder in your project you should have a launchSettings.json file with the following:   { "profiles": { "NameOfYourAddIn": { "commandName": "Executable", "executablePath": "C:\\Program Files\\ArcGIS\\Pro\\bin\\ArcGISPro.exe", "commandLineArgs": "" } } }     This can be SET in Visual Studio with Project Properties -> Debug -> Open Debug Launch Profiles -> New Profile -> Executable.     ... View more

Also look in \\\..\Documents\ArcGIS\AddIns\ArcGISPro ... View more

AddInContent is no longer an option in Visual Studio 2022 for ArcGIS Pro 3.x projects. 🤔 ... View more

Because you have to increment the Add-In date to something 'newer' that what is previously shown. If you don't, ArcGIS Pro will not load your NEW Add-In; rather it will used the cached copy from the last successful run. ... View more

This means you installed ArcGIS Pro as local user vs. 'all' users on the targeted machine. ... View more

While checking on Microsoft Desktop Runtime .Net 8,0,x, ensure you also include the WebView2 requirement. Both of these should be deployed by your IT staff to all members of your GIS Group. It is preferred that these are 'already' installed when you try to load ArcGIS Pro 3.3 or 3.4. SIDE NOTE! ESRI allows users to install ArcGIS Pro per-user if they don't have local admin on the computer. However, the side effect is 'they' will be the only person who can see and run the software on that computer (other than a person with Admin permissions). Side effect, is if you ever do a managed deployment, which goes to ALL USERS, you will have a version collision since the managed update will NEVER see the per-user installation. In office environments using managed software deployments, PER-USER installations are BAD 🙂  ... View more

When installing Microsoft Desktop Runtime .NET 8.0.x ensure you are using a Windows x64 installer, is required. Did the person who installed the software have local admin on the computer? It sounds like you have install on first use turned on as well...but that should only happen the 1st time you start Pro.  ... View more

Other than the locations described above, there must be another location where shared add-ins are cached that is not published. On our case the Solution was to delete the users profile (on the offending machine) and create a new one. Downside, is you lose the individuals preferences (e.g., printers) and this must be done by a third party/local admin on the machine.   ... View more

When you save to PDF you can PRINT or EXPORT to PDF. In Export you can setup options to include fonts in the file vs. being dependent on what is on the end users computer. This is useful for uncommon characters and symbols. ... View more

In this case the user has no C:\Users\[user]\AppData\Local\ESRI\ArcGISPro  or C:\Users\{user id}\OneDrive\Documents\ArcGIS\AddIns\ArcGISPro folder, Yet the shared add-ins are displayed in the interface. I manually copied the add-ins from the source (where they have the [gui-id} folder paths) into the AddIns location and they began appearing in the ArcGIS Pro interface. However, the add-in still throws and error (re: undefined data type). However, everyone else who logins to this _same_ computer has no issues with the shared add-ins.... 😞 ... View more

Version number only uses 3 places (3.3.2), the 4th is ignored or, perhaps, throws an error. ... View more

ArcGIS Pro 3.3. requires Microsoft .Net Desktop Runtime 8.0.X to run. ArcGIS Pro 3.2 required Microsoft .Net Desktop Runtime 6.0.X (which has reached end-of-life). ... View more