CSOM Deprecation
There have been some changes made to the driver in the 2020 edition that should be taken into consideration.
CSOM Support Discontinued
Prior to the 2020 edition of the driver, connections to Microsoft Project using both the CSOM and OData interface were supported, which lead to difficulties in maintaining the two schemas concurrently.
By removing support for the CSOM, connections to Microsoft Project are streamlined due to the lack of special connection properties made specifically for each schema. Also, the OData interface can now perform all of the same CRUD operations that the CSOM is capable of. Lastly, the CSOM is poorly documented and more error-prone than OData.
For these reasons, the decision was made to deprecate support for the CSOM in favor of exclusively supporting the OData interface.
Improved Performance with OData Bulk Operations
One additional advantage of using the Microsoft Project OData interface exclusively is the support for efficient bulk operations.
Microsoft Project data must be checked out, an INSERT/UPDATE/DELETE operation is performed, the changes are published, and finally the changes are checked in.
At times, the checkout step may fail, leading to numerous requests per single INSERT/UPDATE/DELETE operation.
With the driver's batch support, you can dramatically reduce the numbers of requests submitted, since several records can be submitted through the checkin/checkout process at a time.
See Batch Processing