nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

proConfigX: 3.2 and 3.3 Compatibility

KrisCulin

Hi All,

We currently have a configuration for AGP that works against AGP 3.1 and 3.2. 3.3 was just released and we've verified that it works as well (without rebuilding).

I understand that AGP 3.3 is built against NET8. At the moment, we cannot upgrade to target against net8 in order to continue support for 3.1 and 3.2 (upgrading makes them incompatible). We are currently referencing the AGP 3.1 NuGet package.

The problem is with debugging. If we build our configuration project, the proConfigX file is *not* copied to Documents\ArcGIS\AddIns\ArcGISPro\Configurations. This works if I have AGP 3.2 installed.

I'll repeat that - when I build with AGP 3.2 installed, the proConfigX file is copied. If I have AGP 3.3 installed, it is *not* copied.

If the file is not located in that folder, then our configuration does not load and base AGP loads instead. If I copy the file into the folder that was built against AGP 3.2, then the configuration loads. As long as the correct proConfigX file is located there then our configuration loads. I cannot find the proConfigX file that is built when building against AGP 3.3.

This is very frustrating because side-by-side installation is not supported by AGP. It is either 3.2 or 3.3, not both.

Can someone please look into this and confirm that it is a regression? Make sure your configuration (I suspect an add-in has the same issue) is targeting net6 and using the AGP 3.1 NuGet package.

If you have any questions or need more clarification, please let me know.

Kris

Find more posts tagged with

Accepted answers

CharlesMacleod

RegisterAddin.exe was moved to a common folder at 3.3. I suspect that the issue u r running into is that the 3.1, 3.2 Nuget still references RegisterAddin.exe in the Pro bin folder. Addins not using the Nuget reference RegisterAddin.exe via the .targets file in the bin folder so wont experience the same behavior.

For your purposes of u wanting to use the older Nuget, i think if u copy RegisterAddin.exe into the Pro bin folder u should be good to go.

At 3.3, the default location is here: C:\ProgramData\EsriProCommon

All comments

JoeMadrigal

When I upgraded to ArcGIS 3.4 (from 3.2), I also noticed that the registeraddin.exe was moved to ProgramData folder. I then installed the latest patch for 3.4 and the registeraddin.exe moved back to Program Files\ArcGIS\Pro\bin. What is going on here?

KrisCulin

Thank you so much for the quick response. This solution worked perfectly.

I've notified my team members, so they know the work around.

Kris

CharlesMacleod

For your purposes of u wanting to use the older Nuget, i think if u copy RegisterAddin.exe into the Pro bin folder u should be good to go.

At 3.3, the default location is here: C:\ProgramData\EsriProCommon

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.