nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Upgrading to API version 3.0

NateReck

I am preparing to upgrade a Silverlight web app based on the 2.4 API to the 3.0 API and also from AGS 10.0 to 10.1. I am just trying to see what "gotchas" exist that people have run into and how they were handled. Or what were the major hurdles to jump when converting a 2.4 app to 3.0. Thanks!

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

deleted-user-ATjHIWsdQYmT

Any *general* timeframe for a 3.1 release?

DenisT

It's a bit of a race condition and not too often this occurs, so I'm not sure if that should keep you from updating

Well, then I am lucky, because I can see this annoying bug very often.

Morten, Jennifer, thanks for your advices.
Looking forward to 3.1.

AlexanderKhoroshun

Morten, Jennifer,

Many thanks for your responses. Looking forward to see v3.1... and, hopefully, ArcGIS Runtime v.1.0 for WinRT 🙂

Alexander.

JenniferNery

I think as a workaround you can set DisableClientCaching=True. I've seen this happen when setting VisibleLayers property twice where most recent value was overwritten by first value.

SomeGISGuy

This issue has been fixed and will be in v3.1. It's a bit of a race condition and not too often this occurs, so I'm not sure if that should keep you from updating (there are lots and lots of other things that got fixed, improved or increased performance so it's probably worth it).

AlexanderKhoroshun

I'm having the same issue with SL API v.3.0:
ArcGIS Server 9.3

Thanks in advance for any advice from Esri team.

DenisT

There is an issue with 3.0 API.
If you interact with a map, a dynamic layer can send multiple requests.
For example a dynamic layer sends request A, then you change the map scale and the layer sends request B.
The problem is that the request A is not cancelled when the map sends the request B.
So there could be a situation when a request B completes first, because it's a different scale and the map could be much more simple in that scale.
In that case the map renders the request B result image.
But then the request A completes and the map clears request B image and renders the request A image (for the old scale).
In that case the user should pan the map to see the correct image.

The bug was introduced in 3.0, so we downgraded to 2.4 for now.
We are using Silverlight 5 with ArcGIS Server 10, not 10.1.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.