XAML in Blazor SERVER side

[jcbeppler]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

The problem is this:
Developing UI app for web application is complex and irritating to do in HTML/CSS, even simple things are hard to achieve and usually beside all the work done, the result is not so good. In fact is so bad and hard to do that everyone has to use the same templates.
On the other hand, the results achieved with XAML are very good and very simple to achieve, a junior developer is able to achieve outstanding unique results with it.

NOTE: I am talking about an application, not website with a simple menu which display some simple stuff on a table.

Describe the solution you'd like

As the goal of Blazor is creating apps so doing UI development for SERVER side in XAML would be a groundbreaking feature! WPF and WinUI are 2 really good examples of really good development platforms.

Additional context

This request has been requested a few times but always the "bot" mark it as resolved or just ignored.
#10911
#10225
#16321
#5658
#16331
#16478
.......
Just before the suggestion comes: No, people have zero interest in using Xamarin/MAUI Webassembly.

For voting before someone tells me that no one is interested on this feature:
👍 I love XAML, it is better and I would love to use it in Blazor
👎 I love HTML/CSS and want Blazor to keep just with that

[danroth27]

Hi @jcbeppler. We understand that XAML is a popular technology for UI development, but for ASP.NET Core & Blazor our focus is on HTML & CSS based web development. For folks interested in XAML based web development we recommend engaging with the various XAML based communities: Uno, Avalonia, OpenSilver, .NET MAUI.

[jcbeppler]

Please, help me understand this 3 points, I really would like to understand them:
1- All the suggestions mentioned don't do what I asked for, so I don't have a way to solve my problem which is a problem from many people. It is getting common for msft to ignore customer feedback (this became the default, not the exception).
2- Why are all the tickets marked as "completed" or "resolved" instead of "rejected" when they are in fact rejected?
3- The default from Nadella administration appears to be "I don't care to my customers" because yeah, people do pay VS subscriptions so everyone would expect a little bit more effort and at least the ticket to remain open and see if more people do need it.

[danroth27]

1- All the suggestions mentioned don't do what I asked for, so I don't have a way to solve my problem which is a problem from many people. It is getting common for msft to ignore customer feedback (this became the default, not the exception).

As part of maintaining ASP.NET Core & Blazor as free and open source project we have to make decisions about the scope of the work we tackle given our limited resources and expertise. There are certainly lots of things that we could build or support that users might find useful, but we can't do it all. So, we scope the set of problems we can invest in and try to be clear about areas that we're not investing in. That doesn't mean your scenario isn't valid or you don't have a real need. It just means that we are not trying to solve that particular need with this project.

2- Why are all the tickets marked as "completed" or "resolved" instead of "rejected" when they are in fact rejected?

That's a good question! It might be that we're using GitHub wrong? It looks like "completed" is the default way that GitHub closes issues, but we could close issues as "Not planned". I'll start an internal discussion about how we're closing issues to see if we need to alter our current processes.

3- The default from Nadella administration appears to be "I don't care to my customers" because yeah, people do pay VS subscriptions so everyone would expect a little bit more effort and at least the ticket to remain open and see if more people do need it.

We do care deeply about our users' needs, but that doesn't mean we can support every use case. Supporting XAML is outside of our current scope, which is focused on supporting .NET with web technologies. I recommended engaging with other projects that might be more aligned with your use case. For example, I believe Ooui supports a Blazor Server-like mode but based on XAML (it actual predates the work we did on Blazor Server).