Browse our Products

Aspose.Tasks for C++ 26.7 Release Notes

All Changes

KeySummaryIssue Type
TASKSNET-11767Allow passing an instance of DbProviderFactory instead of ProviderInvariantName when using DbSettingsEnhancement
TASKSNET-11768Add reading of Resource Codes from Primavera DB, XER, XML formatsEnhancement
TASKSNET-11782Fix ‘An item with the same key has already been added’ exception when adding more than 1 view to the projectBug
TASKSNET-11770Fix “InvalidCast” exception when Microsoft.Data.Sqlite provider is used to read project from MS Project database.Bug
TASKSNET-11748Fix import of activity codes and UDF from Primavera DBBug
TASKSNET-11584Fix incorrect (multiplied by 100) values in baseline cost timephased dataBug
TASKSNET-11576Fix Task.GetTimephasedData and Resource.GetTimephasedData dont’t cut the resulting timephased data items according to the passed start/end argumentBug
TASKSNET-3634Fix “System.ArgumentException: An entry with the same key already exists” when reading a project from DBBug

Public API and Backwards Incompatible Changes

The following public methods were added:Description
Aspose::Tasks::Connectivity::DbSettings::get_ProviderFactory()Gets an instance of DbProviderFactory which is used to connect to DB. If both ProviderFactory and ProviderInvariantName are set, ProviderFactory has a priority.
Aspose::Tasks::Connectivity::DbSettings::set_ProviderFactory(value)Sets an instance of DbProviderFactory which is used to connect to DB. If both ProviderFactory and ProviderInvariantName are set, ProviderFactory has a priority.

Related issue: TASKSNET-11767 - Allow passing an instance of DbProviderFactory instead of ProviderInvariantName when using DbSettings

When reading a project from a database, the database provider can now be specified by DbSettings.set_ProviderFactory() method.

Related issue: TASKSNET-11584 - Fix incorrect (multiplied by 100) values in baseline cost timephased data

Possible breaking change in logic

In versions prior to 26.7, the values of cost timephased data for baselines were incorrectly multiplied by 100 when stored internally. This fix ensures that the values of timephased data for baseline costs match the values for regular assignment costs.