Migrating to v2019

ASP.NET Maker 2019 is a major upgrade from v2018, it introduces some new features which are not fully compatible with old versions. When you open an old project in v2019, ASP.NET Maker will try to convert the changes for you. However, the conversion cannot be 100% and you'll need to do some updates yourself. Please read the follows carefully, review your code, update and test it before deploying the new scripts to your production server.


ASP.NET Core 2.1.1

Require ASP.NET Core 2.1.1 or newer (including v2.2.0). All previous versions are not supported.

Always use netcoreapp2.1 (or netcoreapp2.2 for v2.2). If you use Microsoft Access, you need to change to ODBC. (.NET Core app does not support OLE DB.)

Please be reminded that since last version (v2018), the EW_ and ew_ prefixes in code are removed, e.g. EW_PROJECT_NAME becomes PROJECT_NAME and ew_ExecuteScalar() becomes ExecuteScalar(). Also, the c prefix for class names are also removed, e.g. cListActions becomes ListActions.

No more Page_* methods (EXCEPT for server events) e.g. Page_Run() becomes Run().


Obsolete Properties and Methods (since v2018) Officially Removed

Some out-dated properties and methods marked [Obselete] since v2018 have been officially removed in v2019. If you are still using those obsolete properties and methods in your server events, you must update your code. The obsolete properties and methods are:

  • The Highlight(string name, object src, string bkw, string bkwtype, string akw, string akw2) method of the DbTable class, you should use Highlight(DbField fld) instead.
  • The SelectTemplate, OptionTemplate and SelectOptionTemplate properties of the Lang class, you should set the Type property as "SELECT" or "RADIO" instead (NOT for used with top Navbar).



ASP.NET Maker JavaScript is now under the ew namespace. The EW_ and ew_ prefixes are therefore changed to ew., e.g. EW_LANGUAGE_ID becomes ew.LANGUAGE_ID.

Method name are changed to the more common camel case, e.g. ew_Ajax() becomes ew.ajax(). If your client side code calls any ASP.NET Maker functions, you must update them.

If you used ew_Ajax() in your client side code, note that the function has been changed, see examples under Lookup Table.


Bootstrap 4 and AdminLTE 3

Bootstrap 4 uses rem (not px) as primary CSS unit, update your font size. Many Sass variable names are also changed, update your theme settings.

AdminLTE 3 now uses Sass also (previously LESS was used), update your theme settings.

Make sure you re-generate all .css files, you can NOT re-use old .css files from previous versions. If you use your own external stylesheet, you MUST update it first.

AdminLTE 3 does not support Layout Options (e.g. Top Navigation which was used as horizontal menu in previous version) any more. There is only one layout now.

NOT compatible with ASP.NET Report Maker 11 (see below).



There is no more icons in Bootstrap 4. Now Font Awesome v4 (not v5) included in AdminLTE 3 is used. Update your icon class names in Menu Editor and server events, if used.


HTML Element IDs and CSS Class Names

The HTML element IDs and CSS class names are changed to the more common param case (i.e. lower case, dash separated), e.g. ewTable becomes ew-table. If you specify them in your custom CSS styles and JavaScript, update them accordingly.


Lookup Cache

This version supports caching the lookup table (if reasonably small) and it is enabled by default. The caching is done on server side so the page may be loaded slightly slower if you have many lookup fields in the table. You may however disable and fine tune this feature by the two new advanced settings, Use lookup cache and Lookup cache count (see Advanced Settings).



There is no more Top Navigation option in AdminLTE 3, the horizontal Menu extension (for registered users) is retired. However, there is a new option Navbar Item for menu items which allow you to put some (or all) menu items at the top navbar, see Menu Editor. You can show all menu items in the navbar on the top of the page, just right click the header of the Navbar Item column in Menu Editor and click Select All. In such case, the vertical menu will be hidden automatically. For mobile mode, the vertical menu is always used as mobile menu.


Language File

There are always new phrases in new major version, make sure you update your non-English language files or some phrases will be missing in Multi-Language projects.


Compatibility with ASP.NET Report Maker

Note that ASP.NET Maker 2019 uses ASP.NET Core >= 2.1.1, Bootstrap 4 and AdminLTE 3 while ASP.NET Report Maker 11 stills uses ASP.NET Core < 2.1.1, Bootstrap 3 and AdminLTE 2, so they are NOT compatible with each other. If you need to use integrated projects, you may consider upgrade your ASP.NET Maker project later. ASP.NET Core >= 2.1.1, Bootstrap 4 and AdminLTE 3 will be supported in next major version of ASP.NET Report Maker, v12.






 ©2004-2019 e.World Technology Ltd. All rights reserved.