Latest Contributions by dotMorten_esri

The approach is the same you use with any view events - the Maps SDK isn't special in this regard. Depending on which UI framework you use, it's slightly different though. For instance MAUI using the MAUI Community Toolkit you can execute a command from an event:   <esri:MapView Map="{Binding Map, Source={StaticResource VM}}"> <esri:MapView.Behaviors> <mauitoolkit:EventToCommandBehavior EventName="GeoViewTapped" x:TypeArguments="esri:GeoViewInputEventArgs" Command="{Binding GeoViewTappedCommand, Source={StaticResource VM}}" /> </esri:MapView.Behaviors> </esri:MapView>   In WPF you can use the Behaviors SDK to do the same thing:   <esri:MapView Map="{Binding Map, Source={StaticResource VM}}"> <Behaviors:Interaction.Triggers> <Behaviors:EventTrigger EventName="GeoViewTapped" > <Behaviors:InvokeCommandAction Command="{Binding GeoViewTappedCommand, Source={StaticResource VM}}" PassEventArgsToCommand="True" /> </Behaviors:EventTrigger> </Behaviors:Interaction.Triggers> </esri:MapView>   In WinUI and UWP, you can bind straight to a method in your VM using x:Bind:   GeoViewTapped="{x:Bind VM.OnGeoViewTapped}"     Prism also offers some documentation on this:  - https://prismlibrary.com/docs/wpf/interactivity/event-to-command.html  - https://prismlibrary.com/docs/maui/behaviors/eventtocommandbehavior.html ... View more

You need the 200.1 Local Server SDK which you can get from the link you posted above ... View more

> With Xamarin Forms and ArcGIS Runtime 100.x we were able to run the tests using .net 6 using the test explorer.  Xamarin.Forms had the same limitation. For .NET 6 it is similar that you need to target net6-windows even with 100.15. That hasn't changed with 200.x.  We've frequently asked Microsoft to improve their test framework to better support both WinUI, iOS and Android, because we realize it is limited, and we don't want to maintain our custom test runners any more than you do. ... View more

I've reproduced the issue. It does appear that the .NET 8 RC2 SDK has introduced a regression and doesn't deploy the native references. The moment I switch back to the .NET 7 SDK things are fine again. ... View more

One more thing to consider in addition to Thad's suggestions: The map you have loaded might default to a maximum scale that is higher than 5000. You can however easily check that if you try and zoom in with the mouse after: If you're not able to zoom in more, it's because reached the default scale limits of that specific map (you can override it by setting the max scale of the layer limiting it) ... View more

Are you remote-deploying from Windows via a Mac, or with an iPhone connected directly to Windows using Hot Restart? Remote deploy works for me with 200.2 - just note that xcode 15 currently doesn't work due to this issue: https://github.com/xamarin/xamarin-macios/issues/19157 (workaround in issue, or downgrade to xcode 14). v200.3 will have official support for .NET 8. ... View more

> So at this point in time, it feels like there is no way to run unit tests against a project that uses both MAUI and the ArcGIS Maps SDK.  The Maps SDK only ships runtimes for Windows, iOS, Catalyst and Android. You _must_ run the unit tests in the context of these platforms, which means executing the tests in the context of an application (similar to how UWP did, but you can probably get your Windows build run un-packaged to run from commandline - see doc on running unpackaged WinUI apps). When you add the UseMaui bit, I believe it defaults to running the apps as packaged - the command line for executing tests in packaged Windows apps is similar to how you'd run UWP unit tests. We run unit tests daily with maui, and we basically launch an runner-app that runs the tests and reports the results back. This is mostly a home-grown system, since Microsoft still hasn't provided a good OOTB solution for executing unit tests on devices and inside WinUI packaged apps. ... View more

Hi Tomas, Thanks for the detailed callstack. That's really helpful. It looks like there are a few cases where Android could return a NaN value from a pinch zoom gesture, that we aren't guarding against. While I don't have a workaround for you, the above is enough information that we at least can get a fix in for the next release. ... View more

> How can i load base map without token?  It really depends on which service you're putting in your basemap. If you're using the ArcGIS Online basemap services they generally require an API Key to load. You can generate one in the developer dashboard. Otherwise look for other various other services you can use that aren't requiring API key. ... View more

>  I could just stick with Framework 4.7.2 and  not move to Net Core for the 200.x release Yes. .NET 6 is optional. .NET Framework is still very much supported, and probably will be for a while. Now there are benefits to moving (performance being one), but again not at all a requirement. ... View more

> Ideally I would expect the images to remain a fixed size with respect to the map, as opposed to shrinking as they currently are. That is exactly how that should work. At a screen scale of 200%, it should render twice the size in raw pixels (but same size in device-independent pixels). Any chance you could share a small simple sample that reproduces this issue so we can investigate? ... View more

I agree that .NET MAUI had some quality issues, but a lot of that has been addressed in v8. The release candidate is already out with a go-live license, so you could get started on it. They made huge improvements in quality. Just to be clear: You don't have to move from .NET Framework to .NET 6 when going to v200. Personally I don't like the upgrade assistant very much. I had more luck just creating a new .NET 6 WPF project and copying that new .csproj over the old one (or moving old files over to the new project. ... View more

You should be fine moving to 200. I'd recommend you briefly upgrade to 100.15, and recompile. Look for any obsolete API warnings and address those. Any APIs that are reported obsolete have been removed in v200, but most obsolete warnings should tell you what to use instead (if you move directly to 200 you will just get build errors for those APIs, instead of helpful warnings). Other than that, you should be able to just change the target to v200. Do note that .NET Framework 4.7.2 is now required, or if you're using .NET, .NET 6 is required (It'll be .NET 8 by the time 200.3 rolls around). A lot of work has been done to UN in the last few releases, so I'd encourage you to go to the 200.x releases. Moving to MAUI is definitely more of a process - but that's mostly around your UI and dealing with mobile requirements - the business logic for the Esri APIs are mostly if not completely identical. ... View more