Apparently someone did, and the ensuing chorus of “No, we don’t want that!” is being ignored.

You can upvote this comment if you want them to provide a proper setting instead of having to edit the registry.

It’s NOT off by default. It’s on/off according to the setting you have for “Receive updates for other Microsoft products. Get Microsoft Office and other updates together with Windows updates”. If you have that on, then auto VS-updating will ALSO be on. The controversy is no developers want auto-VS updating on, even if they DO have that other setting on. Auto-updating Office and auto-updating VS aren’t the same thing at all. I for one never update Windows and VS at the same time, because if something breaks in your app, then how do you know which update broke it if you did them at the same time?

Personally, I dislike the way the UI is declared and bound though (XAML)

You can write the MAUI UI in C#. No need to use XAML anywhere.

Creating MAUI UI’s in C#

He works at Microsoft

@DevLeader@programming.dev @devleader@hachyderm.io

I’ve never used 8, but I liked 10. I especially liked the built-in anti-virus - there was noticeable performance improvement once I got rid of the 3rd party stuff. Absolutely hate 11 though - I’m planning on rolling back soon.

Yeah, the last time I posted about AI stuff I got my first-ever negative net votes here, but it was news and I posted it. Same here. Alvin Ashcraft also posted a link to it, and I said to him that from what I’ve seen so far, this isn’t going to work out any better for them than it did last time. Maybe next time they might learn to ask developers first, BEFORE saying “Hey developers - we need you!”.

Who’s on first? :-)

Still not quite sure what the different design ideas behind Xamarin and Maui is

Xamarin had separate projects for each platform, whereas they’re all together in MAUI. Also Xamarin was tied to .NET Standard 2.1, whereas MAUI uses the latest .NET releases (starting with 5 or 6 - I’m now on 8). MAUI major releases now come out at the same time as Visual Studio updates. Also, as mentioned, MAUI uses handlers, but I’m still trying to work out how you actually use one to create a property (sigh). There was a few, annoying, breaking changes too. e.g. in Xamarin I could define the span and height of an element in a Grid with a single command, but now I have to use two (for some bizarre reason setting the column span is now entirely separate. I ended up writing my own function so I could do it all in 1 line again).

1/2x is also unambiguous. 2a=(2xa) by definition. Has done for at least 180 years. Terms

Nothing wrong with the way it’s written - division before subtraction.

And a bunch of those bugs are for shell, which nobody wants anyway, but for some unknown reason they want people to use it. And newbies don’t know the difference and will raise an issue for “shell” when in actual fact it’s not an issue with shell but with the root MAUI control. The bug I mentioned before about ToolbarItems was initially raised as being a bug in shell, but the bug is actually in ToolbarItems. They should just kill off shell and focus on fixing the actual MAUI bugs.

Well, it depends how you want to look at it. The TL;DR is the number of outstanding bugs has grown.

I remember in the early MAUI days when people were commenting about there being 2000 open issues - there’s now nearly 3,500 open issues. A lot of issues have been closed - there was a period where several I was waiting for got fixed - but even more new ones are getting reported as people transition from Xamarin. A lot of them aren’t “reliability bugs” in the sense that it makes the app crash, but there’s a whole bunch more missing functionality.

Quite frankly I’m surprised they sunsetted Xamarin as planned. All along I was thinking “there’s no way that’s gonna happen on that date with this amount of bugs still open”, but yep, they went ahead and did it anyway. If it were up to me I’d still be using Xamarin, but I don’t have that choice (hence starting up this community to try and reassemble everyone from the Xamarin forum days, and let’s get to helping each other out with our bugs and workarounds - I already got 1 solution to a problem from someone here).

To give an idea of the missing functionality (which was working in Xamarin) you still can’t bind to properties in your ToolbarItems, cause there’s no properties there to bind to! The issue for that is now 2 years old. We were told that we can use handlers for that, but there’s no documentation on how to do that (I raised an issue for that too a few weeks ago). As I said, that’s not one that causes your app to crash, but you still can’t do what you could do in Xamarin yet, so the ToolbarItems look out of place with the rest of your app. FlyoutMenu still has issues too.

“The improvements they’ve incorporated into .NET MAUI indicate that it’s more reliable than Xamarin”

BWAHAHAHA! 🤣🤣🤣 😡😡😡 I don’t know who this guy is, but he doesn’t seem to know much about MAUI/Xamarin other than a blurb someone has given him.

I thought that was gonna happen. 😂 But hey, like I said, it’s Windows Dev news so I posted it. I guess I can put that down as my first net-negative votes. 😂

It is just that here, in this situation, I didn’t get it

I scrolled back to see, and I think that initial one was just someone who disagreed with your suggestion, for whatever reason (like I downvote incorrect responses to order of operations questions. i.e. hearsay which contradicts what’s actually in textbooks and taught), but then yeah, there was some piling on when you asked for an explanation, and I just write them off as “I don’t want to see this” types. At first it bothered me, but in the end I just take out of it that I got more upvotes than downvotes, so just proceed with business as usual then. :-)

Remember the human, and all of that

Yeah, there’s some keyboard-warriors who forget that. You learn to just ignore the downvoters unless, like in your situation, you’d like an explanation as to why your particular suggestion was downvoted by someone. e.g. maybe they know something that you don’t. There was a whole side-discussion about Kagi like that (someone had seen something on a blog, and someone else pointed out the CEO’s response to the blog, etc. - I didn’t read the whole thing… but I didn’t downvote it either ;-) ).

I can’t even recall the last time I downvoted something

I’ve downvoted things which I know are wrong (people love expressing opinions on things they have no expertise on - just check out the threads on order of operations! 😂), and upvote correct things (the whole point to up/downvote is to push relevant things to the top), otherwise neither usually. Sometimes I use upvote to indicate I liked something someone said.

just seems so… lazy

Yep.

And now I am getting downvoted for asking an honest question

Welcome to programming.dev! 😂I’ve had the same happen (technical issue, looking for a solution or workaround, get downvoted). I take it as “I’m not interested in this - don’t ever show me anything about this again” - well, just scroll on by then, not hard. 🙄