Connect for ADO.NET Release Notes History

DataDirect Connect for ADO.NET Release 4.3.0

Only 100% managed code architecture for connectivity to Oracle, DB2, SQL Server, and Sybase using ADO.NET. With the 4.3.0 release, we are supporting several new features.

New Features in ADO.NET Entity Framework Data Providers

  • Security 
    • Support for Credential object for all drivers 
    • Credential objects help to encrypt the password information when stored in the memory in the application.
    • Oracle 12cR2 ALLOWED_LOGON_VERSION=12 support
    • Oracle FIPS support

 

  • Supportability 
    • Improved vanilla Logging to log Entity dll versions

 

  • Installer User Experience 
    • Installer now only requires .NET 4.0 as prerequisite.  Which is the present by default on all windows OS after windows 7 SP3
    • Upgraded Install Shield to latest version IS2016.
    • DPE(Deployment of reports) is now integrated with the installer

 

  • Other Features 
    • Support for Visual Studio 2015 and 2017 [Deprecated earlier versions]

 

  • Performance Improvement
    • Added Native Array Binding support for DB2 LUW and iSeries, leading to substantial performance improvement.

 

  • DB and OS Certifications 
    • DB2 for i V7R3
    • DB2 Z/OS 12
    • SQL Server 2017
    • Oracle 12cR2
    • Windows 10 Creator
    • .NET Framework 4.7

Release 5.3.3 Private Cloud

Progress® Rollbase® Version 5.3.3 Release Notes

Release Date 

April 24th, 2019


  • For information on supported platforms, see here.
  • For Third party acknowledgments, refer product documentation or the installation directory.

Fixed Issues


Following is the list of issues fixed with this release.
Case ID Defect ID Description
  RB-9338 Tenant admin is being redirected to login page when accessing the account settings page.


Enhancement


Following is an enhancement in this release.
Case ID Defect ID Description
RB-9283 XSS is prevented in the Activity Trail section on the system console monitoring tab.


Known Issue


Portal session is being timed-out even if the user is actively using portal (for >= inactive time settings in Security Level).


patch-whats-new

Read Next

What's new