thank you so much for all your efforts, for me i think we need more tutorial for MAUI and not tips & trick. we need simple Project tutorial as to be honest i found challenging to learn Maui as beginner compared to other frameworks as its have the less tutorial than other. please put more effort in tutorial and am sure more people will start adopting MAUI.
.NET 9 is an amazing release with so many features and performance improvements - really impressive! I'm happy to be on MAUI now, seems like it's growing while Flutter's future is somewhat in question.
Today you can build targeting Android, and use the .NET MAUI DevKit extension for VS Code. .NET Meteor has demonstrated working with iOS from Linux, but I'm not sure if that has been shipped.
I have a question, you guys say "single project" but what happend when you need to deploy a Huawei SO, its Android but a different implementation, like Huawei Notifications (Push Kit). There is only a single folder "Android" for Google, but how lives 2 SO Android (Google and Huawei)?
When we say "single project" we are speaking about the project system primarily that enables multi-targeting. We do probably overload the term to also refer to a single "solution" that can target multiple platforms, regardless of how many projects you choose to include. If you're going to target 2 Android TFMs, with differing implementations, then a separate project is probably the easiest approach. We ship a multi-project template if you want to reference that for the setup.
I disagree, XAML is way more readable and comfortable than flutter spaghetti and also you don't have to use XAML if you don't want to, so what are you asking for exactly ?
Here are options for you - writing end-to-end apps solutions using C# only: - using C# Markup - part of the communitytoolkit for Maui - using C# Markup for Uno Platform - using MauiReactor UI - it is the best as it uses MVU pattern to write apps; both the business logic and the UI. Eerything in code in C# using MVU pattern
00:00:32 - Different app templates and types
00:03:05 - Growth overview and stats for MAUI
00:07:58 - Syncfusion controls in .NET MAUI 9
00:10:32 - .NET MAUI/Syncfusion project template
00:14:51 - Component vendors
00:15:20 - Contribution stats + thank you
00:17:07 - .NET 9 new features fluff
00:19:40 - .NET MAUI in .NET 9
00:29:57 - XC Sync (XCode/Visual Studio for Mac hybrid feature)
thank you so much for all your efforts,
for me i think we need more tutorial for MAUI and not tips & trick.
we need simple Project tutorial as to be honest i found challenging to learn Maui as beginner compared to other frameworks as its have the less tutorial than other.
please put more effort in tutorial and am sure more people will start adopting MAUI.
I would really love to see a benchmark comparing CV and CV2 performance.
Good job MAUI team, getting more awesome every release 💪💪
What particular scenarios do you have in mind?
How about AOT compilation? Why is the Publish menu disabled? I want to build a standalone native exe-cutable.
.NET 9 is an amazing release with so many features and performance improvements - really impressive! I'm happy to be on MAUI now, seems like it's growing while Flutter's future is somewhat in question.
Isnt the xaml live preview available in VS Community ?
Can I build a MAUI project on Linux yet?
Today you can build targeting Android, and use the .NET MAUI DevKit extension for VS Code. .NET Meteor has demonstrated working with iOS from Linux, but I'm not sure if that has been shipped.
I have a question, you guys say "single project" but what happend when you need to deploy a Huawei SO, its Android but a different implementation, like Huawei Notifications (Push Kit). There is only a single folder "Android" for Google, but how lives 2 SO Android (Google and Huawei)?
When we say "single project" we are speaking about the project system primarily that enables multi-targeting. We do probably overload the term to also refer to a single "solution" that can target multiple platforms, regardless of how many projects you choose to include.
If you're going to target 2 Android TFMs, with differing implementations, then a separate project is probably the easiest approach. We ship a multi-project template if you want to reference that for the setup.
❤
Any plans for an actual GUI designer?
Source code for the example in video?
Great job!
💯💯💯
25:56 - 99+ binding errors = )
When will i expect like flutter? Xaml is not user friendly need like mobile blazor binding
I'm also waiting for xaml to be abandoned.. Xaml is long-winded and very complicated.
I disagree, XAML is way more readable and comfortable than flutter spaghetti and also you don't have to use XAML if you don't want to, so what are you asking for exactly ?
Here are options for you - writing end-to-end apps solutions using C# only:
- using C# Markup - part of the communitytoolkit for Maui
- using C# Markup for Uno Platform
- using MauiReactor UI - it is the best as it uses MVU pattern to write apps; both the business logic and the UI. Eerything in code in C# using MVU pattern
@@obinnaokafor6252 Excepting own UI framework with component across devices and not the wrapper feature
kotlin >>>>>