What's new in CodeCharge Studio 2.3

The following is the overview of key changes, improvements and new features in CodeCharge Studio version 2.3.

Trial version changes:

• The Trial period was reset to allow those whose previous trial period of CodeCharge Studio 2.x has expired to restart their evaluation process.
• The Trial version now allows for a maximum of 45 pages within a single project.

General changes and additions:

• Extended the character set encoding handling and added Default HTML Encoding project setting.

  The encoding handling was extended to allow specifying different encodings for the HTML pages (templates) than the code files (ASP, PHP, etc.). It is now also possible, though not recommended, to utilize different encodings for different HTML pages.
  Note that if you specify 'Site Language' when creating new projects it will be used to set the corresponding values of the File Encoding and Default HTML Encoding properties of the project.

• Added "Use LIMIT/TOP" property in Server Connection settings.

  Starting with version 2.3, CodeCharge Studio can optionally generate programming code that takes advantage of the SQL LIMIT and TOP clauses to improve application's performance. The specific use of these clauses is database specific but in all cases it limits the number of records being retrieved from the database. For example when working with the record form only one record is being retrieved, while the grid form at maximum retrieves the records up to the last record shown in the grid.

  To enable the use of TOP and LIMIT clauses, set the “Use LIMIT/TOP” property for the particular connection. For backward compatibility purposes this option is turned off by default when opening projects created with previous versions of CodeCharge Studio. However, it is enabled by default for new projects.

  

  Note: when using a connection with TOP or LIMIT, the clause is automatically applied even if custom SQL or custom code that alters the DataSource is used. If you prefer not to use TOP or LIMIT clauses you may create another connection with this option turned off.

• Added SFTP option in project publishing settings as support for secure file transfers.

  When this option is checked CodeCharge Studio will utilize the SSH protocol rather than standard FTP to publish files to remote location.

ASP

• Added new VBScript file upload method that utilizes ADODB.Stream.

  This method of uploading files utilizes a COM object included in Microsoft Data Access Components that is installed on most servers. It is much faster than the previous VBScript upload method, although not necessarily as fast as commercial COM upload components.

• Added support for absolute virtual paths, which can be specified in "#include type" project property. All existing and new projects will now default to utilizing absolute virtual paths as this file inclusion method is now default in IIS 6.0. For more information refer to http://support.microsoft.com/default.aspx?scid=kb;EN-US;332117
• Documentation changes: replaced deprecated function CCToSQL with the ToSQL method. For example:

      CCToSQL(tasks.user_id_assign_by.Value, ccsInteger)

  was replaced with:

      DBIntranetDB.ToSQL(tasks.user_id_assign_by.Value, ccsInteger)

  CCToSQL will continue to be supported for backward compatibility.

Java

• Added support for tld descriptor format version 1.2, which is used when the target server is set to Tomcat 5.

PHP

• Added "Encoding Extension" project property. Either "iconv" (preferred) or "mb" PHP extension is needed to convert strings from one encoding to another. The encoding conversion occurs when loading data into the template library and the file encoding does not match the encoding of the HTML page. For more information on both encoding extensions refer to:
  • http://php.net/iconv
  • http://php.net/mb_convert_encoding

See also:

Key Features of CodeCharge Studio