This document should be read in conjunction with the Release History, which detail items added to, missing, or removed from specific builds.

• Introduction
• Compile Errors
• Old Clarion
• Support for Windows XP Deprecated
• Distribution
• New Features and Changes
  • All
  • Desktop
  • Server
  • API Server
  • Apps
• Changes Required to Convert your app from NetTalk 12 to NetTalk 14
  • Desktop
  • Server
  • API Server
  • Apps
• Populating Settings Control Template

This document works through the major changes between NetTalk 12 and NetTalk 14. It is designed for users, currently experienced with NetTalk 12 to quickly identify and use the new features in NetTalk 14. It covers things that are likely to break when you upgrade your app, and instructions on how to correct the application to allow for a smooth upgrade. It also covers other new features which you may wish to make use of in your application.

If you are upgrading from an earlier NetTalk version, then be sure to work through the upgrade notes for each version, which can be found on the toolbar at the top of this page.

The most common cause for compile errors (in NetTalk class code, or generated code) is because one of the other related tools you are using has not been updated. Especially StringTheory, xFiles, jFiles and Reflection.

StringTheory version 3.62 or later is required.
xFiles version 4.24 or later is required.
jFiles version 3.03 or later is required.
Reflection version 1.23 or later is required.

Invalid Use of Private Data

Support for Windows XP has officially been deprecated. Some features may not work on Windows XP.

1. CLANET DLL has been updated. This should be deployed with your application
2. OpenSSL has been updated. See Deploying a TLS Client or Server for more information on deploying TLS servers and Clients.
3. CaRoot.Pem has been updated. This should be deployed with your application.

The goal of this section is a quick overview of things that have changed since NetTalk 12 which experienced NetTalk 12 users will want to know about.

NOTE: NetTalk uses many of the latest methods and functions in the following products. If you are using these then please update them at the same time.
StringTheory 3, Reflection, xFiles 4, jFiles 3, WinEvent 5, Draw 4, Chrome Explorer 2

All

Desktop

Web Server

Web API Server

Apps

All

1. Nothing at this time

Desktop

1. Add the jFiles and Reflection Global extensions to the app.
2. If you are using HERE Maps then you may want to switch to using the "HERE Platform" login, Authentication and API. If you do this then you can change the authentication, and CLASS on the NetTalk Global Extension,  Options tab.

Server

1. Add the jFiles and Reflection Global extensions to the app.
2. If you have a Settings Control Template on the WebServer procedure, then delete it, and re-populate it. (see below for details.) If you don't have it then add it.
3. Check the WebServer and WebHandler for orphaned embed points. Some methods in the classes have been renamed, or had their prototype changed.
4. If you are using the Maps script, and you are locating the map to the current position, then turn on the Location scripts in the WebServer procedure.

API Server

1. NetWebService Procedures need to be set as Declare Globally.

Apps

1. Add the jFiles and Reflection Global extensions to the app.
2. If you are using the Maps script, and you are locating the map to the current position, then turn on the Location scripts in the WebServer procedure.

Populating a Control template that has SHEET and TAB controls can be tricky. These tips will help;

1. If the control already exists then delete it form the screen. After deleting the control then close the Window editor. Failure to close the window before repopulating results in all the USE Equates being wrong.
2. If your Main Sheet does not have a SETTINGS tab then add one.
3. Add the control template to the settings tab by;
   1. Select NetWebServerSettings on the Control Templates pad.
   2. With a single click place the top left corner of the controls on the top left corner of the Settings Tab. (Nothing will appear to happen)
   3. Move the mouse straight down about a centimeter, and about 3 pixels to the left.
   4. Click slowly, six times. (no more, no less) (about 2 seconds between clicks.) You should then see the control template appear.
   5. IMMEDIATELY, without clicking ANYWHERE else, click the green tick icon and close the editor.
   For a visual example of adding the Control Template see ClarionLive webinar #721, at around the 31 minute mark.