I don't know what specifically triggered this to start happening, but while developing I started noticing late last week that after making GUI changes to an Add-in I am working on, they were never showing up in the actual add-in. After extensive testing to make sure it wasn't an error on my part, I realized that the changes were not showing up because of some new error when building. I verified this by deleting the C:\Documents\ArcGIS\AddIns\ArcGISPro\{add in folder guid} directory and rebuilding the project... I noticed the esriAddInX file is never being replaced. It says the build succeeded but when pro opens there is no trace of my add in.
I am also seeing as soon as RegisterAddIn.exe is run for my add in an exception gets thrown:
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
It seems like this could be a .NET version mismatch ? I have ArcGIS Pro 3.2 Installed and I am building an Add-In targeting ArcGIS Pro 3.1 using the Esri.ArcGISPro.Extensions30 Nuget package. This has been working totally fine until last week when I had to downgrade my version of pro from 3.3 to 3.2 to work with an enterprise geodatabase using Sql Server 2016.
I am really spinning my wheels on this and I have tried a few things to fix it with no luck. Has anyone encountered this before?