C++ Runtime Dependencies

[JeremyBridges]

If anyone has been looking for the best way to deploy the C++ Runtime with your esri Runtime WPF app, here's the content we brought into our app package. We copy from these locations:

32-bit:
c:\windows\syswow64*140.dll
C:\Program Files (x86)\Windows Kits\10\Redist\ucrt\DLLs\x86\*
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x86\Microsoft.VC140.CRT*

64-bit:
c:\windows\system32*140.dll
C:\Program Files (x86)\Windows Kits\10\Redist\ucrt\DLLs\x64\*
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x64\Microsoft.VC140.CRT*

32-bit files go into the ArcGISRuntime100.11\client32 folder. 64-bit files go into the ArcGISRuntime100.11\client64 folder.

[MichaelBranscomb]

Hi Jeremy,

Thanks for sharing this info. A local deployment of the C++ Runtime dependencies is good if you want absolute control over the version that is used by your application. Note you're then responsible for keeping it up to date, in contrast to the central deployment which is serviced by Windows Update. 

If our deployment guide topic is lacking any detail, please let us know and we'll be delighted to address the gap.

https://developers.arcgis.com/net/license-and-deployment/deployment/

Thanks

Mike

[JeremyBridges]

Indeed. We plan to maintain this dependency through our trust in Microsoft's build agents, used from within Azure DevOps. Should be pretty reliable.

As for the Runtime docs, I would ask that "Local install" is explained a bit more. I knew what that meant, but I'm not sure all Runtime developers would. Microsoft is un-helpful there too. But, at least the esri docs could refer to Microsoft's docs on the matter.

https://docs.microsoft.com/en-us/cpp/windows/deployment-in-visual-cpp?view=msvc-160#local-deployment
https://docs.microsoft.com/en-us/dotnet/desktop/wpf/app-development/deploying-a-wpf-application-wpf?...
https://docs.microsoft.com/en-us/cpp/windows/walkthrough-deploying-a-visual-cpp-application-to-an-ap...