New features announced here can usually be seen on our Demo Site
well before the official release, usually within a few days of the announcement here. For current and past releases, please see News
We're working on Version 3.0.0:
- All async DataProviders (SQL & File) along with all code throughout reworked to support async.
- YetaWF on MVC5 doesn't support async child actions, async rendering and async action filters, due to MVC5 limitations.
- YetaWF on MVC6 fully supports async in all child actions, rendering code and action filters.
- Http handlers now fully async.
- NLog support for logging. Includes a custom target logging to SQL table, viewable, searchable with YetaWF's logging browse module.
- Full support for web garden and web farms.
- Module/page editing is fully supported.
- Certain site wide settings require a full restart of all instances (typically Site Settings affecting caching).
- YetaWF version upgrades, new site creation/deletion and authorization role changes, additions/deletions are only supported in single instance mode (no web farm/garden).
- YetaWF stress testing shows excellent web garden performance with more than 1/2 Million full page requests per day (on one server with marginal hardware and 4 Application Pool worker processes at less than 50% overall CPU usage). Single Page Application page updates (as performed by default by YetaWF) are still higher. A web farm on separate servers would be significantly better, although this hasn't been tested (no need, no money, send servers :-)
However, web garden support is somewhat pointless as YetaWF with 1 worker process will run at nearly the same speed processing the same number of requests as a web garden (compared to 4 worker processes), thanks to YetaWF's extensive use of async throughout. A web farm is the way to scale if this should be necessary.
- New Caching module supporting
- distributed caching using
- SQL Server
- file system
- distributed (shared) file system
- New Diagnostics module supporting
- web farm/web garden status display
- display of pending restart requirements based on significant site changes (typically Site Settings affecting distributed caching)
- audit trail of any changes to site data, such as pages, modules, etc.
- inspection of distributed cache and locks
- inspection of distributed file system
- New Page Panel to create overview pages for easier user selection of pages, with icons and links.
- Admin megamenu (overview)
- Configuration settings overview page
- Dashboard overview page
The next version will be released in ?????, 2018. This release still needs a LOT of work and requires extensive testing and stress testing due to all the changes. While we try to maintain a monthly release cycle, this release is a major new version (big boulder, not just a rock). There is no exact or even approximate target date, although we hope to release it by August, 2018.
New In Version 2.8.0:
- Built-in support for "Blue-Green Deployment" using IIS, with instant switchover and just inbound rules (meaning, no restrictions for gzip responses).
- New site is deployed next to currently running site, is preloaded and tested, before instant switchover using a proxy in IIS (use of a load balancer for this purpose is also possible).
- Existing sessions are preserved.
- "Single Page App" is not disrupted and will simply result in a page reload when a new Url is visited.
- Ajax requests are served by the new site for a seamless switchover.
- Site visitors will see no disruption.
- Support for plug-in replacable data providers for all datasets. File and SQL data providers are included.
- New DefaultSkin skin with support for all Bootstrap themes offered by Bootswatch, including much cleanup work for skins so there is no assumption as to background/foreground colors. Implementing a brand new skin is now super simple. You can implement a Bootstrap, Kendo UI and jQuery UI theme or just select one of the predefined themes and customize.
- Consolidated site selector and login selector into Control Panel, reducing UI and Css complexity.
- New PartialFormCss property for skins and modules to add a Css class to partial forms. This is typically used with Bootstrap skins to add the "well" Css class to partial forms.
Additional items will be added as progress is made in their implementation.
This version was released in February, 2018.
Not Immediate, Phased In Over Next Few Versions
- Bower (used just for Kendo UI Core) is being phased out.
Even Longer Term
- Migrate to VS Code to remove dependency on Visual Studio 2015/2017. (low priority)
- netcoreapp support (there are however a few limiting factors from our non-open source use of YetaWF which need to be resolved first). (medium priority)
- Investigation into replacing Kendo UI as it's too "heavy" and jQuery dependent. (medium priority)
- Investigation into replacing jQuery UI as it's too "heavy" and jQuery dependent. (medium priority)
- Use of jQuery Slim and eventually eliminating it altogether. (medium priority)
- A transition away from jQuery to TypeScript with JSX is underway. As jQuery is an integral part of KendoUI, Bootstrap, jqGrid (and other plugins used by YetaWF), this is not a high priority, but new code will take advantage of these new features. (high priority)