Forum Widgets
Latest Discussions
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 Ferguson
WPF: Project doesn't find its own Classes ("tag not found in namespace")
Hi there, I've got a problem that's driving me crazy: c# WPF Custom Controls Project (NET 7), Base Namespace "UserControls". All the controls, styles and Converters existing in the project are in that namespace (I tripple checked, it's the only namespace used). All the controls and Converters are public classes. In the project, there is a Class named "EqualityToBooleanConverter.cs" Additionally, there is a Style file called Button.xaml. I need to use the aforementioned converter here, so I am referencing it like this: <ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:local="clr-namespace:UserControls;assembly=UserControls"> <local:EqualityToBooleanConverter x:Key="ETBConverter" /> Intellisense does find the Namespace "UserControls", in fact, the namespace declaration AND the ressource declaration was done using intellisense. BUT as soon as I compile the project, the following error pops up: MC3074 - type "EqualityToBooleanConverter" does not exist in "clr-namespace:UserControls;assembly=UserControls" I just don't get it, as I said, all the files are in the same project, and they are - as of now - all using the root namespace "UserControls". Everything is fine until I start compiling. What I have tried so far: removing the "assembly"-part of the namespace-declaration changing the compile target from AnyCPU to x86 and back cleaning the solution creating a new solution, and re-adding all the files to it Also noteworthy: The same problem occurs when I try using one of the Usercontrols in that project WITHIN the project itself (like: creating a Window.xaml, defining the local-namespace, and trying to add the control leads to the same error as soon as I compile). I don't know what else could cause this...does anyone have any idea?Can we use Maui.Essentials without Maui UI framework?
Previously Xamarin.Essencials was an independed library that could be used with non-XamarinForms applications. Currently this library was rebranded into Maui.Essentials. Which raises a question, if this library become a part of Maui framework with hard dependency on it, or if it still can be used without this GUI framework. I don't see any references to the Maui framework at the moment except Microsoft.Maui.Graphics. Still, I want to see official confirmation stated somewhere. Use cases: 1. We want to be able to build Avalonia applications and use helpers from Maui.Essentials without referencing whole Maui framework. 2. Same about Uno Platform. It should be possible to use it with Maui.Essentials without Maui framework. 3. I also can imagine applications that are built with "net6-ios/android" targets with native UIs without "Forms" from MAUI. These applications will benefit from Maui.Essentials without unnecessary dependency from Maui framework. Thanks, Max Katsydan.
How to decouple views from view models using CommunityToolKit.mvvm
I am writing my first MVVM app using CommunityTookit.mvvm. I am using as reference the Micrsoft Learning link https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/ioc. This link shows the setting of the viewmodel to the view DataContext using the following statement in the view's .cs file: this.DataContext = App.Current.Services.GetService<ContactsViewModel>(); The problem with this as I see it is that this statement couples the view to the view model, in this case ContactsViewModel. This means that in another app the view cannot be used with another viewmodel without modifying the view, i.e. changing ContactsViewModel above to another viewmodel type. This means that the view cannot be stored in a common library that is shared among different apps. There is a C# Corner example with the older MVVM TookKit that solved this problem using a ViewModelLocator class. This project is found https://www.c-sharpcorner.com/article/getting-started-with-mvvm-light-with-wpf/. The solution is to put the following code in the view's XAML file: DataContext="{Binding Main, Source={StaticResource Locator}}" The source object for the binding is found by looking for a ResourceDictionary that is in the scope of the view and which has an entry whose key is "Locator". In app.xaml which by definition is always in scope we have: <Application.Resources> <ResourceDictionary> <vm:ViewModelLocator x:Key="Locator" d:IsDataSource="True" /> </ResourceDictionary> </Application.Resources> The Dictionary element with key "Locator" is an object of type ViewModelLocator. In the ViewModelLocator class there is a Main property that always returns an instance of MainViewModel: public MainViewModel Main { get { return ServiceLocator.Current.GetInstance<MainViewModel>(); } } In our example, the view's DataContext binds to the Main property of the ViewModelLocator object. The value of the Main property is a MainViewModel object and this becomes the DataContext of the view. We can now in a different app re-use the view without changing it. All we have to do in the next app is to create a different ViewModelLocator object that specifies a different viewmodel in its Main property. The view is now completely decoupled from the view model. My question is, how would we de-couple the view from the view model using the CommunityToolkit.Mvvm? Do we also use a ViewModelLocator class? Is there a more elegant way with dependency injection? Another question I have is, suppose we want to use in one app the same view twice with different view models. An example of where we might want to do this is if we had a view that displayed a chart. It is conceivable that we might want to have more than one view model display its data using the same chart view. I cannot see how to do this in either of the above Microsoft or C# Corner examples.
SendKeys on the WinKeys button
I have looked at MS's list of available send keys on their site, but they don't seem to have one listed for the actual Windows Key. The only solution I found was.... SendKey.Send("^{ESC}") However, the key strokes to show the desktop is Winkey+D But, I can't seem to make using the ^{ESC} work with the letter "D" SendKey.Send("^{ESC}(d)") All I get is the Start menu popping up. So, exactly how do I simulate "Winkey+D" with SendKeys??? Any input will be greatly appreciated
