Latest Contributions by dotMorten_esri

Thanks for confirming. Great to hear those fixes helped you too (our sample viewer has been hurting because of the same issue) ... View more

One more thing: If your installed app isn't launching (ie nothing is happening) it is likely crashing. Open up "Event Viewer" and got to Windows Logs -> Application. There should be some recent Error entries that should give you an indication of what went wrong (note there might be multiple entries for the same error, but they contain different details). Make sure content files etc from your project is included (most importantly the "arcgisruntime200.3\*" folder). ... View more

I don't think this is settable in the project dialogs. I never use those any longer either. Typically you do this in the publish settings instead, but since you're doing some kind of installer project I'm guessing you're not using that.  Anyway you set it in the project file directly. Add the following to a project group> <RuntimeIdentifier>win-x64</RuntimeIdentifier> <Platform>x64</Platform> You could also create platform configurations and have it change based on it. ie <RuntimeIdentifier Condition="'$(Platform)'=='x64'">win-x64</RuntimeIdentifier> <RuntimeIdentifier Condition="'$(Platform)'=='x86'">win-x86</RuntimeIdentifier> Again I don't quite know what kind of MSI project you're using since AFAIK they don't ship one out of the box with Visual Studio, so I don't know how it tries to compile the project. If you use the newer App Packaging projects that creates MSIX it'll "just work". ... View more

Since I see the "runtimes" folder in the last screenshot, it looks like you compiled for AnyCPU (the DLLs you're looking for are likely in the runtimes folder). Try setting Platform=x64 and RuntimeIdentifier=win-x64, and the runtimes folder will go away, and the native assemblies will be placed in the root folder. ... View more

Maui just released a service release with a bunch of memory leak fixes: https://github.com/dotnet/maui/releases/tag/8.0.60 If any view on a page leaks, it'll end up holding on to the entire page, including the mapview, and there's not much we can do to overcome that. If the above update doesn't help, you could actually removing the entire mapview control from the page when navigating away. It won't fix your memory leak, but it'll at least get rid of the largest amount of memory being leaked. ... View more

Do you only see the memory issue on iOS? Is so, do you happen to be using a Toolbar in your app? There are a couple known toolbar memory issues preventing the entire page from getting garbage collected: https://github.com/dotnet/maui/issues/20703 https://github.com/dotnet/maui/issues/22814 They were both fixed in the last week or so, so if you're up for trying out the nightly builds of MAUI that might help confirm/deny if you're hitting this issue.   ... View more

>  Yes, you can deploy it without a license. But  "License for developers Use Only" will be shown forever. I guess your customer wouldn't like it. I'm fairly certain that would be against the license agreement. If you sign into an ArcGIS Portal, you can also get a license key from the portal as part of your login flow in the app. ... View more

Did you try setting the OutSpatialReference property as I suggested? ... View more

@DevinCarlson1 I suggest you post that limitation in the Pro SDK area, since they probably don't look in the Maps SDK forum. ... View more

This was addressed in the 200.1 build of the localservices package, and you can now use "dotnet build" with .NET Framework apps that references this package.   wrt restoring, you can use "msbuild /restore project.csproj" to achieve the same thing. ... View more