You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDK V2 has some features which is not exists in V1 like:
V1 only supports the Composable Commerce HTTP API, but V2 has different packages to support the Import API, Machine Learning API, and the Change History API.
V2 SDK supports ME endpoints.
V2 SDK is auto generated from RAML files like other SDKS which means less maintainability and it will be always up-to-date with backend new features.
V2 SDK is faster than V1 SDK as it’s using System.Text.Json in Serialization and Deserialisation
In SDK V1, you only have to configure clients and inject them in the service container in the App Start, but SDK V2, you can use the injected clients or use the ClientFactory to create clients on the fly.
Comparison of SDK Installation
Package
V2
V1
HTTP API
dotnet add package commercetools.Sdk.Api
dotnet add package commercetools.Sdk.All
Import API
dotnet add package commercetools.Sdk.ImportApi
Machine Learning API
dotnet add package commercetools.Sdk.MLApi
Change History API
dotnet add package commercetools.Sdk.HistoryApi
Comparison of SDK Services Configuration
After packages installation, you have to configure services using Dependency Injection Setup in the application Startup.cs