|
POST
|
> "...people seemed to rely on wrong behavior..." is a veery nice way to say "...people spent days to find workaround for bugs that shouldn't be there and with .NET8 those workarounds cause troubles...". Yup that's fair but maintaining broken behavior for the foreseeable future probably isn't the right thing to do either. At least with .NET 8, it'll be easier to just pick specific versions of the MAUI controls, and not be as tied to the workload as was the case before. So you can choose when to get the bugfixes, or when to stay on older versions.
... View more
12-14-2023
03:27 PM
|
0
|
0
|
1666
|
|
POST
|
Sorry there's no trick to support NET7. I'm not going to promise you MAUI is now perfect but definitely has been greatly improved. It's another reason we weren't too worried about moving quickly to .NET 8, because we knew the benefit of moving to .NET 8 will be big enough that we expect most of our .NET MAUI users to move fairly quickly. Only breaking changes I personally know of were actually bug fixes, and people seemed to rely on wrong behavior, which naturally no longer works.
... View more
12-13-2023
09:24 AM
|
0
|
2
|
2759
|
|
POST
|
We made the decision to move to .NET 8, because .NET 7 support lifecycle ends already in Spring 2024, and we've observed numerous critical bug fixes in the new version of MAUI. This is also on par with the plans announced over the last few years, where we always move to the latest LTS version of .NET (which meant two years on .NET 3.1, then two years on .NET 6, now two years on .NET 8, before moving to .NET 10 etc. Also note that .NET MAUI by itself is on a more aggressive support lifecycle than the rest of .NET is, and for instance already dropped support for .NET 6 in the spring).
... View more
12-13-2023
08:50 AM
|
0
|
4
|
2761
|
|
POST
|
This workaround should no longer be needed with 200.3
... View more
12-12-2023
11:56 AM
|
0
|
0
|
9492
|
|
POST
|
Not sure if you missed it or not, but 200.3 went live last week, and you no longer need the UseCidGraph workaround (unless you use WinUI, but that's on WinUI team to fix - slated for their v1.5 release).
... View more
12-12-2023
11:50 AM
|
0
|
0
|
3290
|
|
POST
|
Could you please retry with the latest v200.3. I believe this issue should be fixed in that release.
... View more
12-12-2023
11:48 AM
|
0
|
7
|
2768
|
|
POST
|
Are you also seeing this if you just call ArcGISRuntimeEnvironment.Initialize() ? If so it's most likely an issue with the native libraries not getting deployed. What is your platform and target framework?
... View more
11-27-2023
11:29 AM
|
0
|
0
|
1683
|
|
POST
|
This is a known issue and is fixed in the upcoming v200.3 release.
... View more
11-22-2023
11:15 AM
|
1
|
0
|
1832
|
|
POST
|
Try adding <UseRidGraph>true</UseRidGraph> to a property group. There's a breaking change in .NET 8 that affects how native assemblies gets deployed (This workaround won't be needed for 200.3)
... View more
11-15-2023
09:13 AM
|
0
|
2
|
3506
|
|
POST
|
Is there a reason you're not using labeling to put the text on the gate? That way there's only one thing to move.
... View more
11-14-2023
03:17 PM
|
0
|
0
|
955
|
|
POST
|
> I do not have an API key set If you're using the basemap styles from ArcGIS Online you need to set an API Key (judging from your code you are). 100.x still had access to the old services but you should have been getting obsolete warnings for a few releases if you were still using those. In 200 those have been removed. If a map doesn't load, look at the output window for clues. Also good to try an explicit load of the map using "await map.LoadAsync()" which should throw an error if there's an issue.
... View more
11-07-2023
02:19 PM
|
0
|
1
|
1801
|
|
POST
|
Sorry no I don't remember the reason for this. However the geocode task can work with many different services as well as local offline datasets, where each could have different capabilities.
... View more
11-02-2023
01:59 PM
|
0
|
1
|
1624
|
|
POST
|
You don't really need a controller for reacting to events (see my other response). For performing operations on the view, this PR in the works might be of interest: https://github.com/Esri/arcgis-maps-sdk-dotnet-toolkit/pull/528 (you could just pull the controller code and have a play with it until this is in the toolkit)
... View more
11-01-2023
03:00 PM
|
1
|
0
|
4818
|
|
POST
|
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
11-01-2023
02:29 PM
|
1
|
0
|
4831
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 05-11-2026 07:05 AM | |
| 2 | 03-19-2026 06:03 PM | |
| 1 | 03-03-2026 04:41 PM | |
| 1 | 02-26-2018 07:53 AM | |
| 1 | 02-26-2018 07:51 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|