Blog: Posts from August, 2016

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(183) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Posts from August, 2016
Friday, August 26, 2016PrintSubscribe
Disabling “Create New” in Lookups

Lookups in applications created with Code On Time offer the ability to create new lookup items on the spot. This allows users to instantly add missing lookup options inside the same page.

The “Create New” action is supported in Lookup, Auto Complete, Drop Down List, List Box, and Check Box List lookup styles.

The "Create New" action is available on all types of lookups.

Pressing the “Create New” action will open the create form for the lookup controller. If a value has been typed into an Auto Complete, Drop Down List, or Lookup input, then this value will populate the relevant alias field in the create form automatically.

Pressing Create New while a value is present in the input will populate that value in the create form of the lookup controller.

The “Create New” functionality can be disabled by clearing the “New Data View” property for the field.

Start the Project Designer, switch to the Controllers tab, and double-click the “Orders / Fields / CustomerID” node.

Editing the CustomerID field of Orders controller.

Clear the New Data View property by clicking the eraser icon next to the value.

Property Value
New Data View N/A

Press OK to save the field. Repeat the above process for fields “EmployeeID” and “ShipVia”.

When complete, press Browse on the toolbar. Once generation is complete and the app opens in your default browser, navigate to the Orders page. Select and edit an order. Notice that all “Create New” actions have been removed.

The "Create New" action has been removed from all lookups.

Friday, August 26, 2016PrintSubscribe
“Auto Complete Anywhere” in Lookups

Touch UI applications created with Code On Time offer powerful lookups that allow the user to activate the grid view of the lookup controller, use auto complete to find a value, or select the value from a list.

By default, auto complete will search for values that begin with the typed-in query. For example, the picture below shows that typing in “es” in the Supplier Company Name lookup will result in finding the single value “Escargots Nouveaux”.

Touch UI lookups will auto complete for values that start with the search query.

Lookups also support the ability to match values anywhere in the value. In order to enable this functionality, the data field must have Search Options configured with the tag “$autocompleteanywhere”.

Start the Project Designer. In the Project Explorer, switch to the Controllers tab, and expand to “Products / Views / editForm1 / c1 – Products”. Double-click on “SupplierID” data field.

Selecting the SupplierID data field of Products controller.

Make the following changes:

Property Value
Search Options $autocompleteanywhere

Press OK to save the data field, and press Browse to regenerate and open the web app in the default browser.

Navigate to the Products page, edit a product, and start typing in the Supplier Company Name lookup. Notice that the typed text will now be matched anywhere in the lookup values.

The Supplier Company Name lookup now matches the auto complete string anywhere in the lookup value.

Friday, August 26, 2016PrintSubscribe
Deploying Web Site Factory Project to Azure

Microsoft Azure is composed of a collection of integrated cloud services. It enables easy storage of databases and deployment of web applications to the Internet, without having to deal with the hassle of infrastructure maintenance. When it comes time to offer your application to a larger number of users, your services can be scaled easily to fit your needs. Azure offers pay-as-you go services to scale up or down to match demand.

Let’s deploy a sample Northwind Web Site Factory project to Azure using Visual Studio 2015.

Start the app generator, click on the project name, and press “Develop” to open the project in Visual Studio.

Opening Northwind project in Visual Studio.

In the Solution Explorer (F4), right-click on the “WebSite” node and press “Publish Web App”.

Publishing a web app from Visual Studio.

In the list of publish targets, select “Microsoft Azure App Service”.

Publishing to Microsoft Azure App Service.

If you have not logged into your Microsoft account, enter your credentials in the login window that appears and proceed to log in.

In the App Service window, press “New..” to create a new resource group for your application.

Creating a new resource group for Azure.

Assign a Web App Name to this deployment. Next to App Service Plan, press “New…”.

Specifying a web app name and app service plan for the azure deployment.

Select an app service plan suitable for your deployment. Every tier provides different compute capabilities and features at different price points.

Please note that a dedicated (non-shared) app service plan must be selected in order for reports to be generated. The smallest available size that enables the use of reporting is “Basic – 1” (B1).

Configuring an app service plan for the web app.

Press “OK” to save the app service plan. Then, click “Create” to create the required Azure resources.

When the process is complete, the Publish screen will open with pre-filled values. Leave the values as default and press “Next” to configure settings.

The Publish configuration has been automatically populated.

Check the box next to “Remove additional files at destination”. This will ensure that the deployment directory will match the local directory.

Enabling removal of additional files at the destination.

Press “Publish” to deploy your application to the cloud. When publish is complete, the application will open in your default web browser.

Including Report Viewer DLLs

If Reporting is enabled in the web application, a server error will be displayed. ReportViewer DLLs must be included in the published app.

Open File Explorer by pressing Win+E, and navigate to

C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.WebForms

Open the folder for the version of Report Viewer required by your application. Applications using “.NET 4.6” require version 12.

Right-click on the DLL file and press “Copy”.

Creating a copy of the ReportViewer DLL.

In Visual Studio’s Solution Explorer, right-click on “WebSite” project node and press “Add | New Folder”.

Adding a new folder to the project.

Assign the name “bin” to the folder. Right-click on the new folder and press “Paste”.

Pasting Report Viewer DLL to the bin folder.

The DLL will copy into the “bin” folder.

Copy two more DLLs, found at these locations:

  1. C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.Common
  2. C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.ProcessingObjectModel

Next, re-publish the app by right-clicking on the “WebSite” node and pressing “Publish Web App”.

Publishing the web app with report viewer DLLs.a

Then, press “Publish” to initiate the process. Once complete, the app will open in your web browser and open the home page of your application running in the cloud.