When I edit the WebMap in my portal, such as adding new layers or configuring Popup, these changes are immediately available for my Web Application. However, when I load the map from the Runtime, the changes are not available when I restart my ArcGIS Runtime application.
It appears that when I clear my IE cache and all historic data, the changes to my Web Map are picked up when I restart the application. While I understand the benefit of caching information on the client, is it possible to disable this caching for metadata about a WebMap so I don't have to clear my cache whenever I make a change to my portal? Or at least make the caching have a shorter expiration?
The runtime uses the caching information the server relays. So if the server is saying "go ahead and cache this for a year", we won't requery for the next year. The server could also be using ETag caching, where we'd query back and say "hey, is this still the valid etag?" and the server could either respond with the a yes or return the new updated version with a new etag to use.
So if you're seeing issues here, it would be the server incorrectly reporting how to cache in its header. I suggest you use Fiddler (www.fiddlertool.com) to better understand what's going on.