Pro Add-in Build Failures

[cdevault_pickett]

I have built an add-in for ArcGIS Pro using Visual Studio 2022 and the ArcGIS Pro SDK (version 3.3). I'm trying to also work on this add-in on a my primary machine which I have never been able to get things to work correctly on. I know the add-in builds on the machine I currently use VS on, but when I open the VS Project on my other machine and build the add-in, all it displays is 1 failed when cleaning and building. On this machine, I can open the Developer Command Prompt for VS 2022 and run msbuild, that works fine. But it would be really nice if I could get it to work in the GUI. Does anyone have any ideas here? Does not seem to be a permissions issue, seems like something might be misconfigured with my Visual Studio install, but after several reinstalls, restarts, etc., I still get faced with this issue. 

[UmaHarano]

Hi @cdevault_pickett 

Can you please give me a little more info about your add-in project?

1. Are you using the Esri.ArcGISPro.Extensions30 NuGet in the project?

2. What is your Pro version? Is it 3.3.3?

Thanks

Uma

[cdevault_pickett]

@sumasuma Thank you for the reply. I'm not using Esri.ArcGISPro.Extensions30 in this project. It is pro version 3.3.2.

Also if I create a blank add-in from a template, it fails to build on the machine in question while builds successfully on the other machine. 

[UmaHarano]

Hi @cdevault_pickett 

Can you please check the following on this machine:

• Check this location to see if you see RegisterAddIn.exe - C:\ProgramData\EsriProCommon
• If it is not there, is it in the Pro install location, bin folder?

Thanks

Uma

[cdevault_pickett]

@UmaHarano Looks like RegisterAddIn.exe is located in the ProgramData folder.

After some more testing. It also seems like a permissions issue, despite that it sounds like you should not have to run anything as an administrator. If I build using the command prompt, it errors with the attached errors when running as me (without entering admin credentials) using the Windows Terminal but if I open the command prompt as an admin, enter credentials it opens with cmd.exe and builds. 

I could of swore I tested this with Visual Studio by opening the project as an admin and not. I could of swore it would not build using either option. Until this morning. Now it builds in Visual Studio if I open it as an administrator, however then it does not install the add-in in my user profile (does not appear in Pro) it must be installing it in the administrator's user profile.