EasyQuery

ASP.NET Core is a totally redesigned version of ASP.NET platform. It got very good reviews from the beginning, so we decided to jump in and create a new edition of EasyQuery for it.
About half a year of hard work and the new version was released.

Unfortunately, we were in vain in such a hurry to support ASP.NET Core. Yes, the new framework got good traction and it will definitely overpass (in terms of popularity among the developers) the old ASP.NET MVC in the near future. However, we still (in 2 years after the release) sale more licenses for old .NET Framework than for Core.
Moreover, since we split our code into 2 branches (old version for .NET Framework and the new one - for .NET Core) the maintenance costs became higher.

I guess the right decision back there in 2017 would be to redesign the current code at first make it cleaner, add the features our users asked for and only then port it to .NET Core without splitting.

However, it was not that bad of course. We learned a lot. We totally redesigned the server-side part of the library (it helped later when we finally moved to version 5.0) and closed a lot of our technical debts. We also moved to the new CI/CD/issue tracking system (Azure DevOps) and totally re-organized the development process.

At the beginning of 2013, we decided to change the licensing model for all editions of EasyQuery. The smaller option (Basic license) remains the same while the most advanced one (Company license) became about 3 times more expensive.
We also introduced a new policy for software maintenance subscription (support and upgrades): a rather small subscription fee for those who renew regularly and a much bigger price for renewal for those who canceled their subscription and decided to return back in some time.
Fortunately, all these changes didn't affect the sales numbers (in terms of the amount of sold licenses) but essentially increased our revenue.

After about half a year of selling EasyQuery WinForms edition, we got a lot of request for ASP.NET (WebForms) version of EasyQuery. So, we started to work on it and in a few months, the first (very buggy indeed) version was ready for release.
The internal architecture, the code itself and the UI were just awful since that was a totally new platform for us and we didn't do web programming before.
However, still, there were some users who were ready to pay for that (I guess with the hope that it would become better soon).
So, we proceed.

.NET framework had been gaining its popularity at that time so we decided to release our home-brewed library for user-centered data filtering as a separate product. So, EasyQuery was born.
We actually already had a similar product (a component library) for Delphi, so EasyQuery became a revision of that library on .NET world.
The first version supports Windows Forms only.