Closed mikelor closed 2 weeks ago
@bijington the ReadMe.Txt modified in this PR is specific to the Maps assembly. See the current version here
I'd be happy to take a look at the XML docs and add an explanation there as well. Here's what was in the Release Notes for the 2.01 Version that caused my frustration. If the sample was updated or it was in the XML docs for the method, I may have resolved my issue earlier. LoL.
That'll teach me for reviewing the changes on my phone and missing that detail. Apologies for that.
That would be brilliant if you could. Thank you
Ok @bijington, when you get a chance take a look. I added some example code to the XML docs. They generated just fine.
Description of Change
Demonstrate the correct way to incorporate .Net Maui Maps for Windows into a multiplatform application.
The 2.0.1 Release of the Community Toolkit Maps component introduced a change that requires the #ifdef Windows directive when compiling a multiple platform application with Maps.
This can cause confusion for people trying to incorporate Maps into the application due to the fact that since Maui 8.0.10 now throws an exception on Windows when using the standard Maps component.
No prior tests for this sample code. This code is a sample.
Linked Issues
Fixes #
2050
PR Checklist
approved
(bug) orChampioned
(feature/proposal)main
at time of PR[X] Documentation created or updated: https://github.com/MicrosoftDocs/CommunityToolkit/pulls
Additional information
Modified ReadMe.txt to illustrate proper way instantiate .Net Maui Maps when using CommunityToolk.Maui.Maps
Tested on Android API 35 (requires Google API Key) - New Requirement Tested on Windows 11
Did not test on iOS or Mac Catalyst