Latest Contributions by dotMorten_esri

Yes a fix was included in v200.8.2 See release notes: https://developers.arcgis.com/net/v200/release-notes/release-notes-for-200-8/

‎05-12-2026

When you pause the debugger, any chance you could go to "Debug -> Save Dump As..." and share the generated dump with us? Feel free to DM it to me (or link to a zipped version of it) Also share which platform you're targeting (.NET version, WPF/WinUI/MAUI, OS etc) and build number you're using. That should help us investigate if there's a deadlock here and what might cause it so we can fix it and/or give you a workaround to unblock you.

‎05-11-2026

.NET 10 is already supported with 300.0 and 200.8.1. No need to wait for the next version. We don't need to actually compile for .NET 10 for it to work with .NET 10. Unless Microsoft makes a breaking change things should just work. For instance I'm pretty sure 200.0.0 or even older releases works with .NET 10 (only difference is we didn't take the time to actually certify that). With 300.1 the difference is for .NET MAUI, .NET 10 will be required as the minimum, since MAUI is dropping .NET 9 support tomorrow (For WPF/WinUI .NET 8+ is still fine)

‎03-19-2026

You're most likely hitting a max-path issue with Windows. The quick fix is to place your source code in a folder close to the root to avoid this, or look into some of the Windows settings to better handle long path filenames: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths For what it's worth we agree the filenames has gotten a bit long, so in the next major update we've significantly reduced the filepath length, so it'll be much less likely that you'll hit this Windows limitation.

‎03-19-2026

Thank you for reporting this. We are aware of this issue and already have a fix in place for the upcoming release.

‎03-09-2026

> Parsing the entire Map object seems excessive You don't need to parse everything. Only the bits you're interested in. The problem with Unknown/Unsupported json is that each release what is unknown/unsupported might change, as more and more things gets known or supported, so you can't really rely on the values when you upgrade. Another downside is that it didn't really fully support a full json tree structure, so it was already somewhat limited. While we considered exposing the full set of traversable JSON objects in the API, all the native maps SDKs already provide great JSON support out of the box (like System.Text.Json), so we decided to just give you full access to all the JSON and let the platform APIs do the work.

‎03-03-2026

Update: A fix has been made, and will be available in the next release. Thank you for reporting this.

‎03-02-2026

Nice find. I'm able to repro the issue and logged an issue for us to investigate and fix.

‎02-23-2026

When you say significantly, how much are we talking? There is an animation happening on each location update to make the moving smooth, which means it can be up to one second behind, but never more. Are you seeing more delay than this?

‎01-07-2026

I do see our bug fix history that something like this was fixed. Are you still seeing this with 200.8.0 ?

‎12-28-2025

You can use geometry engines’ buffer method to do so: https://developers.arcgis.com/net/api-reference/api/net/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Geometry.GeometryEngine.Buffer.html just buffer a point that is in the same spatial reference as the map and it will be perfectly round. If you want perfectly round in the real world (which would likely look distorted in the map, use the BufferGeodesic method instead) https://developers.arcgis.com/net/api-reference/api/net/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Geometry.GeometryEngine.Buffer.html

‎12-19-2025

Yup this is the way. The API fully supports rendering it, but there's not yet a public API for programmatically setting it.

‎12-04-2025

See this blogpost: https://www.esri.com/arcgis-blog/products/developers/developers/create-a-mobile-style-for-native-apps

‎12-04-2025

The required libraries will be deployed with the publish command. The only other pre-requisite you need is the VCLibs, which most likely is already on your system. See https://developers.arcgis.com/net/license-and-deployment/deployment/#define-arcgis-components-to-deploy for more details.

‎12-01-2025

Thanks for pointing out this error in our doc. The correct minimum is 17.12. I'll make sure that gets fixed.

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by dotMorten_esri

Re: Map Freeze after MAUI ShareFileRequest on Samsung

Re: Map lockup on CoreMapView.ViewInsets.set call

Re: NET 10 Support Maps SDK

Re: Could not build for iOS since upgrading to 200.8.1 - Could not find part of the path

Re: Exception in CacheManager

Re: Alternatives for Unsupported / Unknown JSON ?

Re: MapView ignores first left-drag pan after right-click

Re: MapView ignores first left-drag pan after right-click

Re: Current location symbol significantly behind the position from LocationChanged event

Re: Map Freeze after MAUI ShareFileRequest on Samsung

Re: Round Circle MapView

Re: GeometryOffsetEffect equivalent

Re: Character marker support

Re: Do I need ArcGIS Runtime to run a published .NET app on another Windows 11 PC?

Re: Compilation error with basic project

Re: NET 10 Support Maps SDK

Re: Could not build for iOS since upgrading to 200...

Re: MapView ignores first left-drag pan after righ...

Re: Level of Detail for Custom Tile Cache

Re: Level of Detail for Custom Tile Cache