Latest Contributions by dotMorten_esri

One of the constructors of the viewpoint takes a geometry, so just pass in the combined extent to its constructor, and it'll auto-calculate the best zoom to fit that extent. ... View more

Also make sure your receivers supports _and_ is configured to receive raw RTCM messages on its bluetooth port. Not all devices do or is by default configured for it. That's the downside of not using the proprietary apps, where it is on you to ensure the device is configured before streaming data to it. ... View more

I'm assuming you don't have the toolbox app running in the background, and blocking the write? ... View more

I have not tried it on an iOS device. Which receiver are you using? If I can dig one up here, I might be able to try and replicate (EAAccessoryStream is what iOS uses to connect and write to bluetooth devices) ... View more

Is your FeatureTable not of type ServiceFeatureTable? (ie can you cast it to this subclass?) If it's a local non-service table, limiting the attributes doesn't have much effect, since you're not hitting the network. ... View more

What you're really hitting here is a limitation of Microsoft's test framework. To fully run Maui, you need to run as a packaged app on Windows, as a Catalyst app on Mac, and as app packages on iOS and Android. Today TestExplorer does not support running test in this context, because it only supports using VSTest to call into a DLL and not talking to a separate application process (well it does for UWP... see below). The test project you were using and referring to in the window isn't running in the context of how the application will ultimately run (as a packaged / sandboxed app), but merely as a simple console app that the Test Explorer talks to. However to fully run MAUI and ArcGIS Runtime, you will need to run in the context of an application. We cannot run on Mac as a "normal" Mac console app - catalyst is required, and catalyst requires running as an application (sorry I forgot about this detail in my earlier reply). To put it another way: We don't support running on MacOS - we support running on MacCatalyst, and Microsoft's test runner does not today support that. To run a unit test in the context of an application, you need a test runner application. I know Microsoft has their own they are using internally, and we've ported MSTest to iOS, Android and Catalyst to get around the same limitation (search for MSTestX on NuGet). I think XUnit has something as well here: https://github.com/shinyorg/xunit-maui  TestExplorer has the capability to do this (this is how you run tests on UWP, as well as how we used to run unit tests on Windows Phone), but they haven't put in the work to support anything but UWP at this time. ... View more

Building .NET Framework applications with the dotnet cli is not currently supported. Either port your application to .NET 6, or use MSBuild to compile your application from commandline. Is there a particular reason you want to use "dotnet build" instead of "msbuild /t:Build" ? ... View more

Attached is an XUnit project that should work on Windows and Mac (didn't get a chance to run it on Mac, so might need a tweak or two) I did have an issue with setting <UseMaui>true</UseMaui>, but I don't think that's really necessary since we're bringing that dependency in implicitly via the project reference. ... View more

Yeah the problem you hit with Maui is it wants to build a packaged application, not a class library. Running unit tests against packaged applications is a lot trickier, and doesn't work well from within Visual Studio - I've only been able to do this from command line with some scripts (pretty much identical to how you'd do it with UWP from commandline).   .NET MAUI just isn't really in a great state today for unit testing, and we had to rely on a lot of home-built tooling to do it. My recommendation (for now at least) is to build a class library with your business logic that doesn't take a dependency on Maui itself (for most business logic you shouldn't have to), and run normal unit tests against that. ... View more

> addingTargetFramework "net6.0-ios" to unit test project doesn't compile  The Visual Studio Test Explorer runs its tests on Windows, so you'll need to target Windows. In order to run unit test on an iOS device, you need an actual application (as opposed to a class library) that knows how to discover and run tests inside that application project. Depending on which test framework you use, some of them might provide some APIs to help you do that (we ended up writing our own because we didn't find any that really worked well for our setup). ... View more

>  That's why I want to test the connectivity instead of trying to load the card. You could start with NetworkInterface.GetIsNetworkAvailable: https://learn.microsoft.com/en-us/dotnet/api/system.net.networkinformation.networkinterface.getisnetworkavailable?view=net-7.0 Joe's code is doing the same thing - making a request to the service, but won't handle authentication, use etag caching etc, not test if the actual services are up and running (but yes it could be used to see if there's any sort of connection to arcgis.com). The benefit of just loading the map/layers is you won't have to load it later and will save you repeating the requests once you do want to load. ... View more

The issue here is that ArcGIS Runtime is mainly a native library, and deploys runtimes for each OS it runs on. It's not possible to run that in a platform-agnostic way. It _must_ declare a target runtime in order to run. The good news though is that even unit tests runs on a specific OS with a specific runtime in the end. There really shouldn't be an issue with you adding a target OS to your unit tests. If you for instance run your unit tests on Windows, just add the '-windows10.0.19041' to your target framework for your unit test project. In the video you linked to, the main project he's testing also have the OS declared in the targets, and there's nothing wrong with also doing this with the unit test project itself.   From the video you posted, it's even pointed out the limited set of platforms you can run on:   ... View more

I'm fairly certain that text symbols always gets converted to vector CIM symbols. TextSymbols aren't great for sharing, since a certain device or PC might not have the font installed that the text symbol relies on, so those symbols are vectorized so it won't be an issue running on different systems. ... View more