WorkplaceX Scope

The following list describes what is covered by the enterprise business application framework:

  • Data access layer. (Built directly on top of ADO.NET)
  • Data grid sorting, filtering, paging.
  • Autocomplete on every data column.
  • Data lookup on cells.
  • An individual class for every data column. Not only for table.
  • Master detail relationship.
  • Workflow. (For example data save dialog)
  • Content management system. (Ability to read from Microsoft Word documents and display its content on front end).
  • Data annotation.
  • Application navigation.
  • Built in session handling.

Native support

Namespace Framework.Internet contains native support for the following social plattforms:


WorkplaceX runs as a single page application. The core runs independent of the visual html representation.

The main pillars are:

  • Data access layer
  • Component (Label, Button, TextBox)
  • Visual (Html representation)
  • Theme (For example Bootstrap)

Data access layer

WorkplaceX splits the data access layer into two parts. A read and a write channel.Style=”width:;”

Read channel

A screen hardly ever looks completely different than what can be accomplished with an SQL view. Therefore WorkplaceX brings data as straight forward as possible to the display. Writing data back to the database however is a different story. That's where the write channel comes into play.

Write channel

Build generates a source code object for every table and view. It derives from Framework.Data.Record. For complex views which read for example from multiple underlying tables, one would overwrite the default Record.Save(); method.

Separated read and write channels help when it comes to prototyping and rapid application development. A first release can be published without the write channel being implemented. Iterations work better once the customer (stakeholder) sees data on his screen. Entering data comes on a later stage of the project. This approach is normally well understood.


All components like Label, Button, TextBox are Html independent and are arranged in a tree structure. At this stage there is no left, right, top and bottom. Components are dimensionless.

public class ApplicationMy : ApplicationBase { public ApplicationMy() { this.LabelMy = new Label(this) { Text = "Hello World!" }; } public readonly Label LabelMy; } 


During rendering the "dimensionless" component tree is transformed into a two dimensional (2D) grid system. It contains columns and rows. The underlying mechanics works similar like Main method to override Framework.Component.Render();

public class ApplicationMy : ApplicationBase { protected override void Render(VisualCell owner) { VisualRow rowHeader = new VisualRow(owner, this); VisualCell cellHeader = new VisualCell(rowHeader, this); RenderComponent(cellHeader, LabelMy); } } 


On a first stage, WorkplaceX framework renders the html tree, theme independent. This means no colors, no style no nothing. On a second stage the Theme object walks along the generated html tree and enriches it with color and style. This is useful for debug purposes. The second stage can be disabled. Now it's easy to find out if it is for example a browser compatibility issue or a business logic problem. The framework contains an object ThemeBootstrap which renders mobile clients html.

(C) 2015 by; Framework Version=a1.461