topic Re: 200.7 - .Net 9 Release in .NET Maps SDK Questions

200.7 - .Net 9 Release

JoeHershman — Tue, 14 Jan 2025 00:07:09 GMT

Curious if you have a schedule for the 200.7 release, which I assume will be compiled against .net 9.0?

Re: 200.7 - .Net 9 Release

dotMorten_esri — Wed, 15 Jan 2025 17:34:57 GMT

Releases are 3 a year on roughly a 4 months cadence, so that puts the release around April. No specific to share yet, but it gives you an idea.

We already support .NET 9 with 200.6, but 200.7 will require .NET 9 for iOS/Android/Maui only, since MAUI is dropping support for NET8 this spring. The rest will still be net8+.

Re: 200.7 - .Net 9 Release

EdwardZajac — Tue, 18 Mar 2025 16:53:39 GMT

I wanted to follow up on this post as I have looked into this for migrating our current Maui application to .NET 9, but after upgrading, our instance of the Esri.ArcGISRUntime.Maui is no longer working. I tried to see what to upgrade there, but all the dependencies listed for it only mentions .NET 8. Is there another nuget package that is required? I have confirmed we are on v.200.6.0. Any help would be much appreciated.

Re: 200.7 - .Net 9 Release

JoeHershman — Tue, 18 Mar 2025 23:45:06 GMT

I have updated to net9.0 without issues. The one issue I did have was that a library (I believe CommunityToolkit.Maui) required a minimum target of iOS 18. Although, after removing I was able to set back to 17.

I know I had to do a lot of work setting x:DataType in my Xaml to get rid of warnings

Re: 200.7 - .Net 9 Release

dotMorten_esri — Fri, 21 Mar 2025 16:23:07 GMT

What isn't working for you? .NET 9 should work just fine.

Re: 200.7 - .Net 9 Release

EricLiu — Thu, 27 Mar 2025 18:42:23 GMT

Hi, we updated to .NET 9 Maui (ArcGIS 200.5) and started to get the warning / error :

Could not load layer. Error: Concurrent operations from multiple threads on this type are not supported.

From the stack trace it seems like the issue is coming from inside the runtime:

at System.Security.Cryptography.HashProviderCng.AppendHashData(ReadOnlySpan`1 source)
at System.Security.Cryptography.HashProvider.AppendHashData(Byte[] data, Int32 offset, Int32 count)
at System.Security.Cryptography.HashAlgorithm.ComputeHash(Byte[] buffer)
at Esri.ArcGISRuntime.Http.Caching.CacheEntry.HashString(String value)
at Esri.ArcGISRuntime.Http.Caching.CacheEntry.CheckVaryHeaders(HttpRequestHeaders requestHeaders)
at Esri.ArcGISRuntime.Http.Caching.CacheManager.SendUsingCachingAsync(Func`3 sendAsyncDelegate, HttpRequestMessage request, String certificateThumbprint, CancellationToken cancellationToken)
at Esri.ArcGISRuntime.Http.HttpDispatcher.SendAsync(HttpRequestMessage request, HandlerOptions options, CancellationToken cancellationToken)
at Esri.ArcGISRuntime.Internal.RequestHandler.IssueRequestAndRespond(CoreRequest request)
at VertiGIS.ArcGISExtensions.Utilities.LayerExtensions.WaitForLoaded(Layer layer)
at VertiGIS.ArcGISExtensions.Mapping.LayerExtension.OnInitialize()

From https://github.com/dotnet/runtime/issues/93205#issuecomment-2226282536 and https://github.com/robinrodricks/FluentStorage/issues/72,

It seems like the issue may be reusing instances of HashAlgorithm. Is this issue resolved in 200.6 or 200.7 ? Could you help us take a look ? Thanks.