Select to view content in your preferred language

Add-In version conflict

811
5
Jump to solution
03-11-2025 04:47 AM
sonj
by
Occasional Contributor

We upgraded the tool from 2.9 to 3.4 and working fine in the development system but failed while loading in the test system. The error says "The add-in cannot be loaded because it targets and incompatible version of ArcGIS Pro. Current verion 3.4 add-in targets:2.9" 

See the attachment for a better understand.

0 Kudos
1 Solution

Accepted Solutions
RichardDaniels
Honored Contributor

win10-x64 is not supported with Visual Studio 2022 and .Net 8.0.12, use win-x64 instead.

View solution in original post

0 Kudos
5 Replies
KenBuja
MVP Esteemed Contributor

Did you follow all the steps on the migration page from the documentation?

RichardDaniels
Honored Contributor

three possibilities:

1. Did you update your config.daml to target version 3.0 and higher?

<AddInInfo id="{Your GUID}" version="3.0" desktopVersion="3.4.0">

2. In  your .csproj file for your solution ensure the following tags are updated to:

<TargetFramework>net8.0-windows</TargetFramework>
<RuntimeIdentifier>win-x64</RuntimeIdentifier>

3. ArcGIS Pro requires .Net Desktop Runtime 8.0.x, this must be on both your build and deploy machines. Also, all .Net references in you Visual Studio project need to be updated to use 8.0.x -or .Net 4.8 for any  WinForms.

and

4. run the upgrade tool as referenced by KenBuja

0 Kudos
sonj
by
Occasional Contributor

#1 <AddInInfo id="{GUID}" version="1.0" desktopVersion="3.4.55405">

#2 <TargetFramework>net8.0-windows7.0</TargetFramework>
<RuntimeIdentifier>win10-x64</RuntimeIdentifier>

#3 Project->Properties->Target Framework -> .NET 8.0

#4 Downloaded and installed below

  • ArcGIS Pro SDK for .NET,
  • ArcGIS Pro SDK for .NET (Utilities)
  • ArcGIS Pro SDK for .NET (Migration).
0 Kudos
RichardDaniels
Honored Contributor

win10-x64 is not supported with Visual Studio 2022 and .Net 8.0.12, use win-x64 instead.

0 Kudos
sonj
by
Occasional Contributor

Thanks @RichardDaniels, it worked after changing to win-x64.

0 Kudos