Note: Please be aware that during the Alpha \ Beta phases, these nuget packages are not supported via official channels. If you do not experience that, or find missing messages in the CDS only scenarios, please let us know. If your working against CDS Only, you should only need. That said, any of the existing CrmServiceClient samples can be used as a base to start.įrom a scenario point of view, we are particularity interested in any issues or challenges when using these library in either Asp.net Core or Functions scenarios.įor 99% of your applications working against Dynamics, you should only need and. Samples and such will be updated overtime on the PowerApps Samples GitHub Site as we move forward with the evolution of this capability. As with most of our Nuget packages that are intended as tools or for developer consumption, we extensively comment in release notes. We have pushed the first version up to nuget, its tagged as preview and I encourage you to read the release notes we provide with the nuget packages.
This version of the SDK libs supports the following and has the following notices: along with a few additional packages that we are using to split out the Dynamics Sales / Service and Marketing centric messages and helpers from the core CDS platform SDK Today we have posted the alpha version of the on nuget. We are now ready to share this with the larger community for testing and feedback.
We have been working to update this SDK package to better address the needs of the current platform and the technologies that many of our partners who develop client applications to integrate with the Power Platform use. We have continued to support this SDK over the last many years over many versions of our platform. This SDK has existed for a long period and arose from the Dynamics 365 aspects of our platform.
net full framework SDK that we provide for folks to develop client applications that communicate with CDS.