web application generator

Code On Time release 6.0.0.28 introduces the following features, improvements, and bug fixes:

• Advanced two-level menus are now available in Premium and Unlimited editions.
   
• Data views now support "Roles" property to allow additional visibility control. The "Roles" are evaluated on the server and work together with VisibleWhen property.
   
• Property BusinessRules.UserEmail can be referenced as @BusinessRules_UserEmail in SQL and Email Business Rules.
   
• Method BusinessRules.AddMailAddresses has been enhanced to accept "loosely" specified list of email addresses separated with comma and semicolon with optional display names.
   
• jQuery 1.7.2 is now integrated in the client library. The future releases will add support for jQuery UI and JavaScript Business Rules.
   
• Application framework matches methods with RowBuilder attribute first as an exact controller name match to the requested controller and as a regex match thereafter.
   
• Page property Title is now optional. If the value is not specified, then the page name is used.
   
• DotNetNuke Factory will load the projet in correct version of Visual Studio when both VS 2008 and VS 2010 are installed on the same computer when a compilation error has occurred.
   
• Modal forms will retain scrolling when lookup fields are changed.
   
• It is possible to reference master views in the visibility expressions attached to all objects.
   
  The implicit master field can be referenced as
   Master.FieldName

The explicit alternative is
view1.FieldName

• It is now possible to create a soft filter by Null value using SQL Business Rules defined as follows:
   
  if @BusinessRules_Tags is null
  begin
     set @BusinessRules_Tags = 'Tagged'
    set @Region_Filter_Equals = 'null'
  end
  
  The rule will work with Customers controller in the Northwind sample.
   
• Method ControllerNodeSet.CreateBusinessRules now support "name" attribute to allow dynamic creation of "named" business rules.
   
• Removed incorrect reference to aspnet_User controller from the Membership Manager.
   
• Quick Find will work even if Query by Example is set to "False" on the first field in the data view.
   
• Fixed the issue with the "soft" filter being require to have a type of "array of objects".
  

Database web applications may contain multiple pages with a complex navigation hierarchy. Traditional multi-level menus do a good a job of presenting such hierarchies. 

Consider the following web app created from Adventure Works database with Code On Time. The navigation menu has multiple levels reflecting the relationships between database tables. Developers will likely want to change the automatically configured menu structure but will still be forced to create multiple levels of navigation menu options.

A web application can be configured to use an advanced two-level menu.

Start the web application generator, select the project name, choose Settings option, and proceed to alter the layout of application pages under Layouts section.

Choose Advanced Two-Level menu presentation style and click Finish.

Generate the app and inspect the new look of the navigation menu in the browser. The second level of the menu is rendered flat with indentation reflecting the hierarchy. All navigation menu levels are visible and accessible immediately.

The accessibility of menu options can be further improved by breaking them into multiple columns.

Start Project Designer and select Pages tab. Select New | New Page option on the action bar. Enter the following properties and click OK to save the page.

Select  Home link in designer bread crumbs and create another page configured with these properties.

These is the partial hierarchy of the pages in Project Explorer with some of the child nodes under Production page collapsed for clarity.

The highlighted page properties affect the menu presentation.

• If about:blank is found in the External Url property, then the corresponding physical page is not created by the application generator. The menu option will be rendered as a static text.
• It is mandatory to enter “*” in the Roles property. Otherwise the security trimming mechanism will remove the option from the menu at runtime.
• If the CSS class with the name menu-new-column is entered in Custom Styles, then a new column of options is started in the second level of the advanced two-level menu.

The indexes of new pages were selected so that they would precede pages Production | Product and Production | Location.

Here is the effect of the changes. All navigation menu options under Production are rendered in two columns.

If an option of any sub-level is selected, then the user interface of the main menu reflects that.

The second level of advanced two-level menu can be further enhanced with the custom CSS style sheets. Create a custom CSS stylesheet in the project and enter following rules.

div.two-level div.production-menu
{
    background-image: url(../_Shared/Page_Categories.png);
    background-repeat: no-repeat;
    background-position: 110% top;
}

div.two-level div.human-resources-menu
{
    background-image: url(../_Shared/Page_Announce.png);
    background-repeat: no-repeat;
    background-position: 130% top;
    padding-right:70px!important;
}

Start Project Designer and modifying the following pages.

Generate the app, refresh the browser page, and inspect Human Resources and Production options on the top level of the main menu.

These are the examples of advanced two-level menu with other available themes.