Thanks for your reply, I don't mind happening this in Visual Studio, but I'm busy upgrading a 2.30 nopCommerce site to 4.30, and I have it over there deployed on Azure. It is running the latest source, so should it be fixed over there ?
So there's a minor release containing a bug fix and the version is still 4.30 instead if 4.31? The point of version numbers is so that:
a. releases can be identified.
b. determine wether a release is earlier or later than another release
You guys at NopCommerce need better release management, or it will runaway on you and turn into a living nightmare. In addition, minor updates should be released as small, change sets that can be easily applied to a production server to minimize downtime.
I suggest learning and incorporating best practices for release management. NopCommerce has been very successful with a growing core developer team. I suggest creating a release management strategy now before going forward.
I have used your app before and love your product.
I am developing with ASP.NET Blazor WebAssembly and have a tool that
creates code against DB Tables.
Please check website:- https://blazatech.com/
I would love to work on a conversion project of your app.
Blazor webAssembly is the future.
Hope you can use me in some form.