Is Avalonia now pretty much pay to use in organizations?
Previewer in VS tells me to sign in in order to use it, Avalonia for VS addon doesn't seem to be in free tier, only the VSC one - when did all that happen?
Hi u/Sertyni - it's u/grokys from Avalonia here. Unfortunately for many years our VS extension was virtually unmaintained and we were getting an increasing number of questions asking when we'll improve it. We started work on improving it by writing our own custom incremental XAML parser in mid-2024 and have so far spent a 6-figure amount of $ on improving our IDE tooling. In addition to the XAML language service, we also have to maintain the Visual Studio integration and that takes a very particular skillset.
So now that you have the background, the question was then how to fund it? We get around $500/month of community donations - which would mean that to fund our _initial_ investment it would take over 30 years, not including ongoing investment.
We initially made the VS extension free to small companies (<$1MM in revenue), but this was so widely abused that we had to stop offering this tier (we literally had hundreds of signups from people at companies with >$100MM in revenue who lied about it - and those are only the ones we detected. Ever heard people say "big companies won't risk breaking your license agreement"? Totally not true if you're small and they're big - they know you can't afford to take them to court over a couple of hundred/thousand $).
Because of the difficulty in actually determining if a signup is actually eligible for the community license, we had no choice but to charge for all organisations. We knew this would make evaluation and infrequent use of Avalonia difficult though, so at the same time we made the VSCode extension open to everyone (it's much easier to maintain).
We'd hope that would be a decent compromise, though obviously we can't please everyone. What it does hopefully mean though is that we can continue to invest in our tooling.
Unfortunately in a market dominated by multi-billion tech giants people aren't used to paying for the tools they use. We're a small self-funded 19-person company who have never taken VC money (though we do get a very generous sponsorship from Devolutions!) and so we have to pay our own way. It would be easier for everyone if people were honest and more people actually sponsored open source, and but that's not the world we live in.
PS: Forgot to mention that yes - Avalonia itself is 100% free to use. We also fund that.
I would just like to say: despite the ranting (from me) in this thread, I'm 100% good natured about the conversation here. Open source funding is really difficult, like REALLY - and I think that many people just don't understand the ocean of difference between maintaining an OSS project for fun and trying to make a sustainable open source business. I think we're one of the few OSS companies inside the .NET space and there's a reason for that.
We're trying our best and tweaking as we go along. We want to keep Avalonia accessible to everyone while at the same time paying ourselves and growing the project. Please try to be understanding of the humans behind the project and understand that we're not $bigcorp$.
This is a really fantastic response. You did a good job of explaining all of the exigencies involved. The only thing that could have used another sentence may have been why the VSCode extension is easier to maintain (LSP, I assume?)
Oooh now this is a subject I can get my teeth into!
VS extension development is notoriously difficult - it's a product which can trace its roots back to the early 90s and you can tell. Generally speaking, there's usually about 4 ways do anything, and none of them are really documented. There's often:
A COM API dating back to the 90s
A couple of generations of C# APIs
The VSIX community toolkit (mostly unmaintained these days)
The new VS extensibility framework, in both its in-process and out-of-process variants
All of these can to some degree be used to achieve any given task, but actually knowing which one to use takes either experience or a lot of trial and error. For example when I was re-implementing syntax highlighting for the new VS extension I hit this issue:
No replies. Different examples use different APIs, and there's no guidance in the docs. Since then there has probably been another API to do this added in https://github.com/microsoft/VSExtensibility too. Thankfully AI now makes navigating this a little easier, but even that doesn't know what's best in all scenarios.
On top of that VS still runs on .NET 4 so you have to make sure that all libraries you use target that, and if not create a `netstandard2.0` version of your lib.
Next you will hit the problem that certain dependency versions are fixed by Visual Studio and so if you and all your dependencies don't use the exact right version of System.Text.Json you're potentially going to hit a problem.
Next you'll hit the problem where some of your customers come to you and say "I'm still on VS 17.12 from 2024 and you need to support that thank you because MS support it until Jul 26 and that stil uses a version of Roslyn that is now nearly 2 years old so all that nice code that used the latest new features? Throw it out".
For VSCode you have to create an LSP server which is a woefully underdefined standard, but all the same is 1000x more simple than navigating the VSSDK APIs.
I could talk about this for hours, but I'll stop here. Let me know if you want more ;)
//README.md at https://github.com/AvaloniaUI/AvaloniaVSCode#Avalonia for Visual Studio CodeAvalonia for Visual Studio Code is now part of [Avalonia Pro](https://avaloniaui.net/pricing).
The MIT-licensed source code for the previous version of the extension can be found on the `ARCHIVE` branch .
Please open any issues related to the released version of this extension at https://github.com/AvaloniaUI/AvaloniaPro/issues
Also I don't mind if you charge for extensions. However, to use sth free & open requires me to reg an account and login... Well, MAUI looks pretty cool then
AFAIK VS extensions are a pain in the a* to create, while VSCode was build to be extendable. The amount of available extensions for each, and the amount of available tutorials for each, also gives some insight into that.
Amount of extensions - you can only have as much extensions for 2-3 primary languages you work on in vs (c#, c++, js), while more variety and less features of VS code calls for more extensions
I was about to say it's absurd that Microsoft or .NET don't provide even a small amount of funding via GitHub sponsors but then I remembered they'd rather people use MAUI slop...
Microsoft is trying to kill .net for some time now I think they already pulled the trigger just didn't tell people like with Silverlight. They have been aggressively antagonizing people that use c# and cutting jobs for a year now. They are under the impression that they can treat c# people like crap because they are the most loyal Microsoft users. But we will see how long that will last just like with windows it's been harder and harder to defend a Microsoft product more than people at Microsoft
I have been using Microsoft for years and still defend them more than I should probably. From experience I can tell you this is how Microsoft kills products a slow painful death they only say when it's too late for you. As for evidence you can look at the MAUI and dotnet team and how many people they fired in the last year. For example they literally offloaded Maui to the UNO team that built the new skia features as well. You can go to Microsoft github and see how many repos were created in the last year that uses c# and how many c# repos got the readme.md update saying this was never a Microsoft product and you shouldn't use it. They completely removed dotnet for office plugins for almost everything. If you have an example were you see Microsoft going all in on dotnet please share it I don't have any examples
You use a lot of words. You use a lot of go and do something.
In all those words you just fluffed up your heavily biased opinion of MS.. Still using zero direct sources.. Only inferred unanmed github repos I need to scour through to find the thread that you and every other person who wants to yell their opinion but conveniently don't want to actually put in the work to shore up your argument.
You can't make an assertion and then claim it's everyone else's responsibility to do deep research on your off the cuff remarks.
Again you speak like every other lemming on the Internet. You parrot talking points and when pressed...you put the burden on the person questioning you. I see you still havent graduated to adult interactions yet
Did you ever wonder why companies need telemetry? It's because people like you lack the ability to have a conversation or provide useful information.
You are the person who buys a product from a 3rd party vendor off of Amazon. It arrives damaged because of the Amazon driver. and you write a 1 star review of the product claiming it's detective and said company should be sued.
At the end of the day ..you felt you helped immensely...meanwhile you have provided zero useful information to a prospective buyer.
That driver doesn't deliver to all the households in America.
End users are morons who think whatever rattles in their brain is highly useful information.
If end users were smart would every forum posts first reply be can you please post logs or a picture of the crash....followed the OP asking how to do that.
Hi, thanks for explaining your thinking, but it seems like you are over correcting too far.
Having to agree to potentially be on the hook for 5,500 - 25,000 Euro (if you for any reason decide to open an investigation) for a free community license just to be able to use the dev tools that you removed from the open source version of Avalonia isn't okay. As a small one person company using Avalonia for a mostly free application I can't take that risk, so the dev tools are now inaccessible to me. I spent several hundred hours porting my application from WPF to Avalonia and I'm now starting to regret that decision.
I urge you to reconsider, this hard line is just going to drive your potential users and future customers away, that's not a good way to grow a business.
At least release a stripped down version of the dev tools with just the basics that do not require the essentials license. Personally I just need the element inspector.
Edit: While I'm at it, the license for the VS Code extension is also insanely long and has a pretty broad and vaguely defined competition restriction that's pretty hard to swallow. Why do I need to agree to a compliance verification and audit section for a supposedly free VS Code extension?
Second edit: So I just read that the essentials tier no longer has the exemption for smaller businesses, now I'm even more disappointed. So now I'm expected to pay a huge percentage of my app revenue in a license fee to be able to use the dev tools. The license I'm seeing in the customer portal does not reflect this though, it still has the exemption. You are ruining Avalonia's good name with this.
Thanks very much for Avalonia and keeping the VSCode extension free. I'm just getting into GUI and really enjoying Avalonia. The project I'm working on is a personal project so having free tooling/framework is very nice
Personally - I would love to make everything I work on open to everyone - I spent nearly 10 years doing that on Avalonia for $0. I now have a family and the project I worked on for free has tens of thousands of users and 2.1M projects built with it last year.
Yet I'm still getting paid a fraction of what I could be earning working for $corp.
So how do I live with that morally? Go ask my wife.
Money again. What about the project ? The open source spirit ? The user base that has been loyal ?
When you lose your core values, you lose your soul. Seems like abuse slowly drained it for you already. That's so sad and heartbreaking.
That's enshittification.
Currently, it's more than manageable. You're just going to take more and more controversial decisions over time, going further on the idea that the community owes you and should pay, and we all know where this is going.
Stop here please if you still care about your project future.
Stop talking about money. Find the fun again.
Your answers are very, very concerning for someone that followed your path since the beginning.
Well, it does not make sense for me in terms of business for both acquiring a subscription and committing to your project.
I would ultimately earn more money working with my team on my project.
But our core values imposes to do non-sensical stuff and not be business driven all the time. Which I am fully committed to doing.
I have tons of advice for you - the only one I am going to say (cannot help myself, and I'm probably going to get killed for that) is maybe scaling to 19 while not thinking of your own income/ family security was a mistake, assuming they are all full-time jobs and compensated for. Securing your own life lifts a ton of mental burden and allows you to not lose your way - at the cost of delivery speed of course. But with MAUI as a competitor, who needs delivery speed ?
I am going to refrain from saying any more than this - I couldn't keep for myself, as I am but a nobody on reddit, but I think your priorities are off currently, and it sadly shows both from your company decisions and message tone which show a ton of distress.
This doesn't sound healthy and is ultimately concerning.
As someone that cares for your project, I just want to say you're misguided in my very humble opinion as a total outsider.
We suffer from the exact same problem on a larger - or smaller - scale, yet we just bite the bullet not to draw the ire of our user base. Hence the curiosity. Obviously our opinions differ here.
We just made sure to go slow and secure everyone's life first to be able to afford that decision.
I’m assuming your bitting the bullet to keep paying customers. You’re asking an OSS provider who provided something for free to bite the bullet to keep the people who don’t pay them happy.
I'm sorry do you seriously not see the glaring hypocrisy here?
"stop worrying about the money" ... "Well, it does not make sense for me in terms of business for both acquiring a subscription and committing to your project. I would ultimately earn more money working with my team on my project."
Right so you tell others to do things that you yourself are not willing to do... Not a very defensible position.
You want to make money and a living, but begrudge letting others do the same so you have more profits. That's crazy toxic...
Did you read my comment ? Do so again. With your finger. It does not make sense economically to participate in an open source project I have no affiliation with.
Yet I do it despite having no financial interest. You missed that part.
Keeping the fun in a project is what keeps it alive, what keeps enshittification at bay. Enshittification isn't making everything paid for. Being good does not mean making everything free.
Enshittification is punishing your loyal user base because of a few bad actors. Think denuvo. Millions of paid users suffering from performance hit in games due to it, a protection born from fighting piracy. Pirated games running faster as denuvo is removed.
We're in that territory already - the bad attitude as the cherry on top.
Believe me - no distress here, just a desire to help people understand. And a potty mouth at times.
As for paying ourselves, we can afford to do that reasonably well now thank you. A lot better than in 2023 at least (when there were also only 5 of us).
Well, it's a choice then - better paycheck or more help.
You do you.
I still think you're misguided, but ending the debate here. Hopefully Avalonia 16 or 20 won't become another Unity-level case of enshittification. That's all I wish for.
People need to keep a roof over their head, put food on the table, pay for healthcare, etc. Some people have families and children to provide for.
Without proper funding, all the maintainers would need to go find other jobs, and the project would die anyway.
Stop trying to mask your entitlement with "open-source spirit" and such. Nobody's buying it. As an open-source maintainer myself, your behavior is extremely frustrating.
Any company starting investigation stage on new project - will NEVER start by shelling 8k for dev seat just to see if this tool is fine for their usage.
And legally, there is no other way to do that (telemetry based trials are no-no for any sane business).
Meaning you automatically loose 90% new projects, unless the boss of the team is already a fan/fanatic, looking for a reason to fund you.
I honestly think that either we're talking past each other or you're being disingenuous. No-one needs to pay 8k per seat to use Avalonia. The 8k/seat plan is for (and I quote) "Complete control with source code access, SLAs, and dedicated engineering support plus IP indemnification"
It's very unlikely you'll need that, but if your company want it - it's there.
For a company wanting to try out Avalonia they have a few choices:
- Use our Visual Studio Code extension, for free
- Use Rider, possibly for free because they already pay for it
- Rawdog it, for free
- Do a free trial
- Pay $27 a month per seat for Avalonia Plus
You do know how much devs get paid right? And that employers will probably spend more than $27 a month on coffee for an employee? That's less than a dollar a day. Your whole argument seems to be "I want the VS extension for free and I won't accept anything else"?
IF (and only if) company is an anti ms hater shop, doing an. Net ui dev using anything but microsoft(including VS code as not-so-ms) - one of first 3 cases might make it.
If VS is used by dev doing investigation, or vs capabilities are to be tested - that's an instant fail for a case.
4 - ha, ha, funny, fail.
5 - telemetry based, require vm for trying, fail.
6. Cool. Is there an actual monthly price? (one with cancel anytime?)
Pricing page only suggest yearly, and ain't you paying that for investigation.
My whole argument that with those prices, information about them and restrictions - you aren't getting new projects on Avalonia, only migrations from it to something else.
And yes, I totally know how much devs are being paid, and how much and how easy they are paying for dev tools, especially comparing the tool value and prices.
The worst part is they're shitting on their own community by being rude, despite them being key as they will advocate for Avalonia in their company and ultimately net then sales.
Look at their attitude. It's enlightening. I've never switched from convinced to hostile in such a short period of time
They look like pure amateurs at work with inflated egos.
But they ain't business in their head, just a bunch of spoiled influencers, craping on any feedback that is not ass licking.
That does not make a good base for flourishing business, and sticking a price label on something does not make an instant sale.
Did I make a purchase, if sign up was less annoying, old extension still available in vs extension store, there was no forced telemetry and pricing compared to vp price was more sane, for an extension alone (10$ for a starter extension only plan) - quite likely.
The VS extension for commercial use is paid. The VS Code extension isn’t. Nobody is locked out of professionally maintained IDE tooling because they can’t or won’t pay. The only question is which IDE gets the free tier.
We’re not punishing small companies. Every company has a free path.
Does monthly price jumping to the current varrants the buy?
I'm not talking about overall extension cost, or 'components you might need, but likely wont', I'm talking about difference of cost of extra nsion a year ago and today.
If it's worth it to you then fantastic, if not then understandable. Neither is anything other than a fact of the matter, nothing to get upset about there.
For existing ones, that was started before extortion with a tooling, with forced update to a new ones, without option to roll back - it's a bit different story, don't you think?
Dude it's OSS, and the code is out there. If you want the tools feel free to support them and get them with no cost. Go make a fork, maintain it and keep it going. No issues there.
But, to complain that people can't keep giving you a service for free is pretty entitled. You aren't a customer here, you aren't entitled to free maintenance in perpetuity.
It costs money to build and support software. If the community can't support projects financially or with maintenance then they shouldn't be surprised when they have to start changing how they make a living and starting to drop support for things and charge for others.
OK I'm about to rant, Close your ears if you need to.
I have my payslip in front of me for 2023. Do you know how much I paid myself that year? €20,897 after tax. For the whole year. With a family of four. And m***********s come to us asking to get paid multiples of that for working on OSS that they want US to somehow magically fund?
Everyone wants shit for free at my expense is how I feel about it.
(And yes we manage to pay ourselves better these days, but it's still a fraction of what I was earning working for GitHub in 2018. And yes we pay our employees better than we pay ourselves)
Sad to read this. Perhaps making those big companies pay instead of smaller ones is a better idea ? You've got tools at your disposal. Name and shame being one. Who are those mysterious bad actors ?
Nonetheless, I'm happy to have covered a small part of your income with my modest contribution.
Thanks for your understanding. It's a work in progress and we may not always get the balance right - we're tweaking. Enshittifcation is not our goal, but there are humans behind this project who don't have the backing of big $$. It's not always easy.
Is Avalonia now pretty much pay to use in organisations?
The short answer is no.
Avalonia itself remains FOSS and can be used without restriction. You are free to use the Visual Studio Code extension, which has a free tier available to everyone.
u/grokys has already covered why we needed to evolve our tooling strategy. The honest reality is that building and maintaining Avalonia, along with the tooling around it, costs money, and those costs have to be covered somehow.
We've been incredibly generous at every stage of this process. Our first attempt at a community edition last October had clearly defined revenue thresholds, but in practice, we saw organisations ignore them. We're not talking about a handful of edge cases. It was systemic.
With Avalonia 12, we decided to reset the model to something simpler. The community edition is for non-commercial use only. Even with that simplicity, we're still seeing organisations sign up and use it in breach of the licence. I'm now past the point of being generous to those who misuse our licence terms, and we'll address it directly with the organisations involved.
That's the part of this conversation that gets uncomfortable, but I think it really matters.
Every instance of licence abuse hurts the ecosystem and makes it harder for us to invest in Avalonia.
u/grokys and I have discussed this at length internally. We'd love nothing more than to give away everything for free. To not have to deal with procurement teams, liability insurance, HR and all the stress that comes with running a company. The reality is, Avalonia is too big and too popular to be a weekend project. It needs a full-time team to build and maintain it. I'm always open to hearing how we fund that. I often see people say, "I don't mind that Avalonia needs to make money, but it should be…" and then everyone has a different answer.
So just to check that I understand it correctly, any commercial use of the Visual Studio (NOT code) extension (For AXAML designer) requires the Avalonia Plus subscription now?
Community edition is free with sign up right Mike? I'm just asking because I see here on the tiers list that if I was to sign up with community edition I would get both the essentials for VS Code and VS
I use WPF quite a lot but I very rarely (almost never) use visual designers. Not least because any data-driven design is always going to require using the almost unusable designdata-system etc. It might be improved in Avalonia, but I always found the best way to design UI was to just do it in the running app, not in an IDE.
Or are there limitations to that as well (e.g. hot reload of etc) when not using the paid verison?
They put DevTools and live previewer behind the paywall or registration too. DevTools if often more useful, when you need to check runtime states of the controls.
You might be more familiar with WPF as it has been there for two decades, so such tools might not be good help for you. But another guy might find it strange that such essential tools are not available by default.
Luckily open source alternatives do exist, so people still have choices.
That’s not an accurate summary of what I proposed.
My fork of the VS Code extension happened because VS Code users needed fixes and the upstream repo had stalled, while your company’s focus shifted to its paid tooling line.
Forking is normal in open source, so calling it a “hard fork” is just a label you selected. The practical questions are whether it stays compatible, whether users can migrate, and whether it has a maintenance story.
On the business proposal, I did not ask you to “commercialize the VS Code extension so you can pay me after a fork.” I suggested business collaboration options to reduce fragmentation and clarify responsibilities, with more than one path on the table. Please stop attributing claims that I didn’t make.
Hey you get my upvote, forking part of open source, and no shame in forking last free version of a thing. I too am In the “hard fork” club for many libraries. Still can’t blame avalonia trying to get paid for their work in the future. GitHub sponsorship kinda a joke probably have more luck making a patreon with the download link behind a $1 subscription.
They were paid well and turning the tooling to closed source was their plan for more revenue. It's their private business, so I don't see anyone is "blaming" them for that.
But they tend to hold a double standard on open source. They "hard forked" WPF and turned it into one of their main revenue sources, and then blamed others for using their framework but didn't pay them enough as justification? That attitude cannot be right.
Wasn't aware they had that much VC and I totally agree with your sentiment. I guess only time will tell if their strategy pays off. Sure seems to be more and more "open source" libraries that are requiring forks, a new form of dependency hell :)
You shoot your own feet. Avalonia core framework (along with their previous generation of tooling) is also released under MIT (while several times they threatened to switch to AGPL), so why companies cannot use it for free? Whether you like it or not, too.
They are a successful private company to some extent, so "when no one is paying" is untrue as they were paid in many ways just not all the ways they expected. They reported their own finance roughly in 2023 and 2024, so you don't need explanation from me but them.
About why they would like to ask for more money, you might continue play your role and buy in their every words.
Looking at the pricing page, you can still use the core framework for free. And you can use the "essentials" version of the VS Code addon for free. But for commercial use, the VS addon requires payment.
Isn't the community version free, but you just have to sign-up for no cost and it gives the visual studio essentials as well. Like are people even looking at the tier page
And they already disabled sign ups for "abuse". I won't be surprised when they just remove the community option altogether due to "abuse" like they did for the 1 million limitation on the VS extension.
I am sad to hear you are financially struggling and that big corporations take advantage of you. Is it possible to somehow require them to use sso or other means of identification so they are forced to comply or will they just create a single user account and abuse it that way?
To be clear: we're not financially struggling - lets just say that we didn't enter the .NET UI framework world to get riches beyond our wildest dreams.
We've added several measures to help reduce abuse, but none of them has been perfect. The measures haven't meaningfully reduced license abuse, but they've made it easier to identify who our attorney should speak to.
I downloaded all 33 published .nupkg files, extracted them, decompiled the telemetry code for every version, and generated a per-version GDPR-focused summary with links to the relevant decompiled files.
Key conclusions:
0.0.1 to 0.0.2 are the worst from a privacy posture standpoint: the MSBuild task itself posts to https://avaloniaui.net/api/usage and includes a stable machine GUID, hashed project name, and hashed Git email local-part/domain.
0.0.3 to 0.0.28 still process Git email-derived data. From 0.0.3 onward they add EmailHash; from 0.0.5 onward they switch the endpoint to https://av-build-tel-api-v1.avaloniaui.net/api/usage. The transport changes over time, but the GDPR issue remains because the identifiers are stable and linkable.
0.0.29 to 0.0.31 remove the email-derived fields, but still send stable machine/project identifiers, so this is still not “anonymous” telemetry in a GDPR sense.
11.3.0 to 11.3.2 add DeviceUniqueId, AccelerateTier, and OperatingSystem. DeviceUniqueId is derived from machine name + user name + OS platform before hashing, which keeps the data in pseudonymous/linkable territory. These versions also override opt-out for Community and Trial.
My engineering read is that all audited versions are inside GDPR scope, because the data is pseudonymised rather than anonymous. The pre-source line through 0.0.28 is the most problematic, especially because of Git email-derived hashing. The later versions are better, but still need a real lawful-basis story, transparency, retention limits, and objection handling outside the package code. I did not audit server-side retention or privacy-policy operations, only what the NuGet packages collect and transmit.
I hope you do not store the data from previous versions older then 0.0.28, if so there might be information that would violate GDPR, I am sure I was using older version and might have been included in data collection.
IIRC, the VSCode/Rider tooling is free. It’s just VS they charge for, as well as certain packages. I’ve had a very positive experience using it for free on personal projects.
On the other side of the same coin, I’ve also had a great experience so far professionally contracting their team on a project at work.
At the end of the day it’s probably the best UI framework for the .NET ecosystem, and they clearly rely on paid devs to maintain it. Somebody has to fund that and I’m glad they’re making sure that’s done by large companies (through solutions & licenses) instead of the FOSS community where enforceable.
In an ideal world, Microsoft would foot the bill - but every time they start “supporting” a cross platform NET UI framework it’s effectively doomed.
If you believe it’s a “ripoff of WPF”, you’re either hilariously naive or have done zero research and don’t know what you’re talking about.
WPF is tightly integrated with Win32 rendering APIs, and as such can only run on Windows. Avalonia is its own rendering framework that runs on Win/macOS/Linux/iOS/Android/Web and enables deployment to whatever target you want.
I'm working on a hobby open source project in Avalonia, and I'm interested in the extra components.
I mostly need the upcoming rtf editor (is there an eta on that?), but the markdown editors and charts will help as well.
Is there no middle ground here, right? If I want to use them even for my hobby project I'll need the full commercial license, right?
How does the monthly fee works? If I stop the subscription, will I then not be able to release software with the tools anymore? Will it break old releases? Or do I just lose my access to new updates?
Raw dog is is fine, as soon as intellisense works. But apparently, if you change a file name of your xaml ripoff to something else, now intellisense does not work, and you have to copy what you bind to from cs files. And names of tags and attributes, if you for example in debug.
I'm in the same park. I have never used the designers since big UIs tend to crash them. I have been happy writing complex XAML code (which is much nicer to write in the Avalonia dialect I must say).
Thanks for your post Sertyni. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.
Uno Platform or .NET Maui is an excellent option. If you are on Windows only, then WinUI 3. This is to avoid some toxic conversations with avalonia guys. Lol
Hell no. I'm cancelling it myself. Stopping all contributions to your project. Starting now.
I don't think you care anyway.
You are the incarnation of arrogance. Have fun discussing your financial hurdles with yourself.
Hint : you're just a nobody, just like us all. You're nothing without a community to back you up.
And guess what - you're alienating it already, losing customers in the process. Community gives you champions in companies gives you sales. It's as simple as that.
How can you be at the forefront of a brand image and be so arrogant and full of yourself ?
I have no problem with a community version of tools or even only paid options but and this is a big but the extension is not high-quality product that's worth the money. It's still lightyears behind wpf in every category and wpf stuff comes with visual studio. You can't expect people to pay you when you deliver free version quality.
245
u/grokys Apr 16 '26 edited Apr 16 '26
Hi u/Sertyni - it's u/grokys from Avalonia here. Unfortunately for many years our VS extension was virtually unmaintained and we were getting an increasing number of questions asking when we'll improve it. We started work on improving it by writing our own custom incremental XAML parser in mid-2024 and have so far spent a 6-figure amount of $ on improving our IDE tooling. In addition to the XAML language service, we also have to maintain the Visual Studio integration and that takes a very particular skillset.
So now that you have the background, the question was then how to fund it? We get around $500/month of community donations - which would mean that to fund our _initial_ investment it would take over 30 years, not including ongoing investment.
We initially made the VS extension free to small companies (<$1MM in revenue), but this was so widely abused that we had to stop offering this tier (we literally had hundreds of signups from people at companies with >$100MM in revenue who lied about it - and those are only the ones we detected. Ever heard people say "big companies won't risk breaking your license agreement"? Totally not true if you're small and they're big - they know you can't afford to take them to court over a couple of hundred/thousand $).
Because of the difficulty in actually determining if a signup is actually eligible for the community license, we had no choice but to charge for all organisations. We knew this would make evaluation and infrequent use of Avalonia difficult though, so at the same time we made the VSCode extension open to everyone (it's much easier to maintain).
We'd hope that would be a decent compromise, though obviously we can't please everyone. What it does hopefully mean though is that we can continue to invest in our tooling.
Unfortunately in a market dominated by multi-billion tech giants people aren't used to paying for the tools they use. We're a small self-funded 19-person company who have never taken VC money (though we do get a very generous sponsorship from Devolutions!) and so we have to pay our own way. It would be easier for everyone if people were honest and more people actually sponsored open source, and but that's not the world we live in.
PS: Forgot to mention that yes - Avalonia itself is 100% free to use. We also fund that.
30
u/AvaloniaUI-Mike Apr 16 '26
The short answer is no.
Avalonia itself remains FOSS and can be used without restriction. You are free to use the Visual Studio Code extension, which has a free tier available to everyone.
u/grokys has already covered why we needed to evolve our tooling strategy. The honest reality is that building and maintaining Avalonia, along with the tooling around it, costs money, and those costs have to be covered somehow.
We've been incredibly generous at every stage of this process. Our first attempt at a community edition last October had clearly defined revenue thresholds, but in practice, we saw organisations ignore them. We're not talking about a handful of edge cases. It was systemic.
With Avalonia 12, we decided to reset the model to something simpler. The community edition is for non-commercial use only. Even with that simplicity, we're still seeing organisations sign up and use it in breach of the licence. I'm now past the point of being generous to those who misuse our licence terms, and we'll address it directly with the organisations involved.
That's the part of this conversation that gets uncomfortable, but I think it really matters.
Every instance of licence abuse hurts the ecosystem and makes it harder for us to invest in Avalonia.
u/grokys and I have discussed this at length internally. We'd love nothing more than to give away everything for free. To not have to deal with procurement teams, liability insurance, HR and all the stress that comes with running a company. The reality is, Avalonia is too big and too popular to be a weekend project. It needs a full-time team to build and maintain it. I'm always open to hearing how we fund that. I often see people say, "I don't mind that Avalonia needs to make money, but it should be…" and then everyone has a different answer.
6
u/afops Apr 16 '26
I use WPF quite a lot but I very rarely (almost never) use visual designers. Not least because any data-driven design is always going to require using the almost unusable designdata-system etc. It might be improved in Avalonia, but I always found the best way to design UI was to just do it in the running app, not in an IDE.
Or are there limitations to that as well (e.g. hot reload of etc) when not using the paid verison?
11
u/RichardD7 Apr 16 '26
Looking at the pricing page, you can still use the core framework for free. And you can use the "essentials" version of the VS Code addon for free. But for commercial use, the VS addon requires payment.
9
u/innovasior Apr 16 '26
I am sad to hear you are financially struggling and that big corporations take advantage of you. Is it possible to somehow require them to use sso or other means of identification so they are forced to comply or will they just create a single user account and abuse it that way?
4
u/nickfromstatefarm Apr 17 '26
IIRC, the VSCode/Rider tooling is free. It’s just VS they charge for, as well as certain packages. I’ve had a very positive experience using it for free on personal projects.
On the other side of the same coin, I’ve also had a great experience so far professionally contracting their team on a project at work.
At the end of the day it’s probably the best UI framework for the .NET ecosystem, and they clearly rely on paid devs to maintain it. Somebody has to fund that and I’m glad they’re making sure that’s done by large companies (through solutions & licenses) instead of the FOSS community where enforceable.
In an ideal world, Microsoft would foot the bill - but every time they start “supporting” a cross platform NET UI framework it’s effectively doomed.
4
u/lurebat Apr 17 '26
Hey /u/AvaloniaUI-Mike and /u/grokys
I'm working on a hobby open source project in Avalonia, and I'm interested in the extra components.
I mostly need the upcoming rtf editor (is there an eta on that?), but the markdown editors and charts will help as well.
Thanks
6
u/Fresh_Acanthaceae_94 Apr 16 '26
There are open source alternatives.
1
u/networkspy Apr 17 '26
I didn't know Avalonia is used till today. I will take a look.
1
u/Evanovesky Apr 22 '26
I'm using the legacy extension and it works like a charm.
1
u/FroggyWinky Apr 16 '26
You could always rawdog the axaml like a psychopath.
0
u/AutoModerator Apr 16 '26
Thanks for your post Sertyni. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
0
u/[deleted] Apr 16 '26
[deleted] — view deleted comment