Unique Device Identifier in MAUI
I am looking for a way to get a device identifier in NET MAUI that is cross platform compliant between Android/iOS/Windows. I originally had this code working in Xamarin Forms with the following: Android Context context = Application.Context; id = Settings.Secure.GetString(context.ContentResolver, Settings.Secure.AndroidId); iOS UIDevice.CurrentDevice.IdentifierForVendor.AsString().Replace("-", ""); Is there anything currently or planned in the future for use in NET MAUI. Thanks In Advance, Stuart FergusonFinally Edge Chromium for Xbox One?
As per reports Microsoft's Edge Legacy browser is going away by 2021 and will be replaced with Chromium based browser, I would like to get an update on Edge Chromium for Xbox One. Since their Browsers in Microsoft's ecosystem will be replaced with Chromium based browser, what about Edge for Xbox One? Or is it impossible for the Microsoft team to port it into UWP or don't want to give heeds? People have been requesting this from long time in Xboxinsider Reddit forum and here but no luck with straight answers!Make Movies & TV App Multi-instance - allow to play more than 1 video at the same time
Make Movies & TV App Multi-instance - allow to play more than 1 video at the same time in Movies & TV App just like Photos app that you can open multiple pictures and have them side by side, make Movies & TV app the same so we can open more than 1 video file at the same time. Upvote this on Feedback Hub app: https://aka.ms/AA7uft1Add Email translation to the Mail app on Windows 10
I need to work with people with different languages and the emails I receive are sometimes in languages other than English, I have to manually copy and paste the Email to Google or Bing translate. I think Mail app should have this feature built in using Microsoft translate so make life easier for us. please upvote this feedback on Feedback Hub: https://aka.ms/AA7qgyx
OS versions Supported in dotnet maui
These are the tags used for defining OS version supported by maui app: <SupportedOSPlatformVersion Condition="'$(TargetFramework)' == 'net6.0-ios'">15.0</SupportedOSPlatformVersion> <SupportedOSPlatformVersion Condition="'$(TargetFramework)' == 'net6.0-maccatalyst'">15.0</SupportedOSPlatformVersion> <SupportedOSPlatformVersion Condition="'$(TargetFramework)' == 'net6.0-android'">31.0</SupportedOSPlatformVersion> <SupportedOSPlatformVersion Condition="$(TargetFramework.Contains('-windows'))">10.0.19041.0</SupportedOSPlatformVersion> <TargetPlatformMinVersion Condition="$(TargetFramework.Contains('-windows'))">10.0.17763.0</TargetPlatformMinVersion> But how to define min version and target android version on Android in csproj file. The min version is only defined for windows over here. But not for iOS, Android and Mac. Can someone please explain these lines and how to set the values correctly for each OS.
Migrate UWP App to MAUI Windows: Error after update with MSIX
I currently have a Xamarin Forms UWP App in the Microsoft Store. In the next months I want to update it to MAUI. For testing purposes and ensuring that all stored data are still available within the app, I want to simulate the Update of the Xamarin Forms app to MAUI with side loading for Windows. After installing the MAUI-msix-Update, an error appears: Is this a general problem or do I have a specific issue in my manifest? Sample app: https://github.com/reinhardlackner/SampleUpdateMauiApp Debugging is working correctly (I can start the UWP-App "SampleUpdateApp.UWP" in Debug mode... and after closing it I can start the MAUI-App "SampleNewUpdatedApp") - and the saved click-data from the UWP app are shown in the MAUI app: Sideloading-Update does not work: a) SampleUpdateApp.UWP - Right click => Publish... Sideloading Use test certificate Install UWP app appxbundle-file App opens => OK b) Install MAUI App as Update SampleNewUpdatedApp - Right click => Publish... Sideloading Use same certificate Create MSIX x86 publishing profile and version is 1.0.1 (update of Xamarin 1.0.0) Start created msix-Package and click on Update: Error message is shown: App installation failed with error message: Deployment Add operation with target volume C: on Package E965F79B-76C7-47E0-8308-4A503105EDE0_1.0.1.0_x86__ab06nvn9z6x6m from: (SampleNewUpdatedApp_1.0.1.0_x86.msix) failed with error 0x80073CF3. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x80073cf3) If the Xamarin app was not installed before, the MAUI App can be installed correctly: Does anybody have an idea why the update installation is not possible? I assume it could be related with the Manifest-File... Manifest UWP: https://github.com/reinhardlackner/SampleUpdateMauiApp/blob/master/SampleUpdateApp.UWP/Package.appxmanifest Manifest MAUI: https://github.com/reinhardlackner/SampleUpdateMauiApp/blob/master/SampleNewUpdatedApp/Platforms/Windows/Package.appxmanifesthow does MAUI handle cross-platform gesture recognition
specifically how is it implemented for each platform and where can i find the code for each platform in regards to this gesture recognition for example, for MacOS i assume there would be some custom NSView implementation with overrides for the following TouchesBeganWithEvent TouchesMovedWithEvent TouchesEndedWithEvent TouchesCancelledWithEvent and for android i assume there would be similar with custom View implementation and OnTouchEvent method override i do not know for windows nor linux as i have not experimented with those platforms yet specifically i assume the gesture API MAUI provides is truely cross-platform and has no platform-dependant behavioural differences (with some exceptions for certain gestures for example a mouse or stylus CANNOT perform a two-finger scroll gesture however would be implemented via the scroll-wheel if present on the mouse on a mobile-device a two-finger scroll gesture does not make sense since it is usually just one finger for scrolling on a trackpad two-finger scrolling makes sense however regardless of HOW it is implemented, the api would provide a platform-independant way of tracking how much the user has scrolled, possibly accounting for some sensitivity setting the user can modify at will similar to pointer-acceleration settings for large and small monitors and high dpi and low dpi monitors
