(Mis)adventures with upgrading .NET Pro SDK with VS 2017 Community

AndrewQuee

With the recent release of Pro 2.5 I thought I would be able to easily update the SDK extensions in Visual Studio 2017 to continue development.  Right?  Wrong!

Here some pitfalls I found you may wish to avoid, read on if you'd like to avoid wasting time climbing in and out of the traps.  Installation was relatively fresh install of VS2017 used exclusively for two Esri projects under Pro 2.3 and no other SDKs.

It started when I downloaded the Pro 2.5 SDK.  The SDK is no longer an automatic installer/updater but works through updating the extension in VS (official Esri instructions).  However this didn't work at all - after downloading the update and showing update pending "Click Close to dismiss the dialog and exit Visual Studio." I closed it... for step 6 "The VSIX Installer dialog will appear."  and nothing happened.  No hidden processes running, just a silent desktop.

This is a known problem with VS2017.  No matter what I did including esoteric hints from StackExchange et al about closing the IDE in a certain way/procedure, first putting on my wizard robe and hat, making sure VS was fully updated, etc it would not start the update process, and when the update was chosen again, it would faithfully tell me it was about to update the SDK then troll me by doing nothing at all.

(as a side-issue Windows 10 also did not update automatically to install the required .NET framework 4.8 and had to be done manually)

Eventually I found some hope in a Repair of VS.  After spending several hours(!) reinstalling 446 updates it wiped the previous Pro SDKs and gave me a vanilla VS.  Yay     Finally, I was able to choose the SDK and when VS closed, the VISX installer dialog appeared.

On reflection I should probably have just completely ignored all the documentation and advice from MS and done an end-run around VS by directly running the proapp-sdk-utilities.vsix and proapp-sdk-templates.vsix that came with the SDK download from Esri.  Not tested, but I suspect it would be faster than dealing with the above bargewaffle.  Yes I am salty Microsoft, I want those hours of my life back..

GKmieliauskas

Hi Andrew,

I have started from the GitHub information about ArcGIS Pro 2.5 SDK (https://github.com/esri/arcgis-pro-sdk/wiki). So my experience was a little bit different but with wasted time.

Wiki text:

hRequirements

The requirements for the machine on which you develop your ArcGIS Pro add-ins are listed here.

.NET Framework 4.8:

• With the release of ArcGIS Pro 2.5, the minimum .NET target has been changed from 4.6.1 to 4.8. What does this mean for you and your add-ins?
  • Existing add-ins, already deployed, will work at 2.5 with no change to their forward compatibility.
  • New add-ins created at 2.5 will require the minimum target framework set to 4.8 or they will not compile (this is the default setting in the Pro SDK).
  • Existing add-ins which are recompiled at 2.5 (e.g. because a code change was made) will also require the minimum target framework set to 4.8 or they will not compile. Note: As always, if an existing add-in is changed for any reason, the desktopVersion attribute in its Config.daml file should be changed to reflect the version of Pro it was last compiled against, in this case, now 2.5

VS2017 max .Net Framework version 4.6.1. So there is one way to install VS2019.

Now look at the other Esri sources for developers: ProGuide Installation and Upgrade · Esri/arcgis-pro-sdk Wiki · GitHub 

It talks about VS2017 and VS2019. I believe in first source because I can't compile my application with VS2017 and SDK 2.5. So I came back to SDK to 2.4. It takes time take back to ArcGIS Pro 2.4.3 and SDK 2.4. 

And remember as wrote Uma uncheck "Automatically update this extension" option for ArcGIS Pro SDK extensions.

Colleagues from Esri could you please explain real situation?