Can you see if there is a problem with getting ESRI map tiles in your software.
We have been using your you WPF Maps in commercial software for about 5 years. About 48 hours ago they all stopped working, not only for every one of our WPF products but also for the new Blazor Maps. This includes software released years ago and so it isn't any recent change in the code. I called ESRI technical support and they don't see a problem with the server. The Main ESRI URL we use is
https://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer
I would appreciate any help as we are inundated with customers complaining the map backgrounds no longer work and we don't yet know why.
I have an update. It looks like ESRI stopped supporting http and now reroutes to https. The https results in the WPF software throwing exceptions. The blazor maps are working fine with https.
What is the best way to fix this problem.
Hello Richard,
Thank you for the update that using https request for blazor fixed the issue. For WPF may i know which exception you are getting ? May be application need to enable some kind of security constrain ,which i am not sure yet until i see the exception i can provide more information.
Thanks so much for tracking this down. The fix you provided works.
Hello Richard, I am able to reproduce the issue and I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 274207.
I have created a private case C-00224085 for you to link this bug. You can access the provate case and see the progress f the issue from your infragistics account.
For a time being As a workaround I tried this after InitializeComponent in the constructor ,and irworks for me . May be you can try at your end too.
InitializeComponent(); const SslProtocols _Tls12 = (SslProtocols)0x00000C00; const SecurityProtocolType Tls12 = (SecurityProtocolType)_Tls12; ServicePointManager.SecurityProtocol = Tls12;
Regarding the issue ,the next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
Regards,
Divya Jain
This is WPF not winforms. Here is an image of the exception.