Upgrading from 3.x

Top  Previous  Next

In order to stream-line the API and to provide greater consistency between the components there have been some changes to the API syntax between version 3 and version 4. Version 4 has been designed to automatically recognise and convert version 3 code as much as possible and in many cases version 3 code will run virtually unchanged under version 4.

Architectural changes

The biggest single change between version 3 and 4 is that the components no longer run out of their own virtual folder but are now instead deployed alongside your own application code in the same application folder. This means you need to make the necessary deployment of DLL's and changes to web.config files in each application that you use DbNetSuite controls.

Upgrading a version 3 client control implementation

The importing of the client-side library needs to be changed from referencing the dbnetgrid.js  / dbnetedit.js file in the DbNetGrid/DbNeEdit virtual folder

<script src="/dbnetgrid/dbnetgrid.js"></script>

to referencing the the DbNetSuite client-side script and CSS handlers.

<link rel="stylesheet" type="text/css" href="dbnetsuite.css.ashx" />
<script language="JavaScript" src="dbnetsuite.js.ashx?mode=compat"></script>

Note the addition of the mode=compat argument to the script handler. This will run the client-control in compatibility mode allowing version 3 code to be run virtually unchanged.

Upgrading a version 3 server control implementation

To upgrade a version 3 server control to version 4 simply requires changing the tag prefix from

<%@ Register TagPrefix="Grid"  Namespace="DbNetLink.Web.UI" Assembly="DbNetLink.DbNetGrid" %>
<%@ Register TagPrefix="Edit"  Namespace="DbNetLink.Web.UI" Assembly="DbNetLink.DbNetEdit" %>

to

<%@ Register TagPrefix="DNL"  Namespace="DbNetLink.DbNetSuite.UI" Assembly="DbNetLink.DbNetSuite" %>