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
This repository contains the code for the Microsoft.PowerPlatform.Cds.Client and its supporting assemblies and classes.
14
+
This repository contains the code for the Microsoft.PowerPlatform.Dataverse.Client and its supporting assemblies and classes.
12
15
13
16
**IMPORTANT NOTE**
14
17
15
-
**The CdsServiceClient cannot be built outside of Microsoft**
18
+
**The Dataverse ServiceClient cannot be built outside of Microsoft**
16
19
This is due to a set of dependencies on nuget packages that are internally available only. At some point in the future, we will expose the supporting nuget packages when we have updated our server infrastructure to support plugin development on .net core.
17
20
18
-
19
21
This encompasses the contents of the following nuget packages:
@@ -35,30 +37,29 @@ We are using this effort to for a few key things we have wanted to get done for
35
37
36
38
<b>We are currently in ALPHA.</b>
37
39
What does this mean?
38
-
Alpha means that we can and will change the api surface, namepaces and behavior from time to time. this is mostly driven by feedback from users of the client (you). During this process we are also working though ports of many internal tools and will adjust things based on the needs of those tools were it make sense.
40
+
Alpha means that we can and will change the api surface, namespaces and behavior from time to time. this is mostly driven by feedback from users of the client (you). During this process we are also working though ports of many internal tools and will adjust things based on the needs of those tools were it make sense.
39
41
40
42
We encourage you to read the release notes we provide with each nuget packages. As with most of our Nuget packages that are intended as tools or for developer consumption, we extensively comment in release notes.
41
43
42
-
At this time: (12/05/2020)
44
+
At this time: (01/20/2021)
43
45
The alpha version of the SDK libs supports the following and has the following notices:
44
46
45
47
* .net full framework 4.6.2, 4.7.2, 4.8 and .net core 3.0, 3.1
46
48
* We now support all authentication types from CrmServiceClient, ( Client\Secret, Client\Cert, UID\PW Noninteractive, UID\PW interactive.)
47
49
* MSAL Port has been completed, this Lib is now using MSAL 4.3+
48
-
* The Namespaces of areas WILL change. We do not know what they will change too just yet but they will change before we “release” this.
49
-
* The Assembly Names Will likely change at least once more.
50
-
* The Message types that are part of the client have been reduced to CDS Core server messages only. Things like “QualifyLeadRequest” have been removed to their own Nuget package ( Microsoft.Dynamics.Sdk.Messages )
50
+
* The Namespaces of areas may change. We do not know what they will change too just yet but they will change before we “release” this.
51
+
* The Message types that are part of the client have been reduced to Dataverse Core server messages only. Things like “QualifyLeadRequest” have been removed to their own Nuget package ( Microsoft.Dynamics.Sdk.Messages )
51
52
* We will likely ship more extension packages that will contain the “CRM” messages, though over time, we will likely split the namespaces of those messages up based on service line, think Field Service or Sales or Customer Service, etc..
52
53
* Plugin Development using this Client is NOT supported at this time.
53
54
54
-
From 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.
55
+
From a scenario point of view, we are particularity interested in any issues or challenges when using these library in either Asp.net Core, Azure Functions, and Linux based scenarios.
55
56
56
-
We believe forthe vast majorty of applications working against the older dynamices sdk libs, you should only need Microsoft.Powerplatform.Cds.Client and Microsoft.Dynamics.Sdk.Messages.
57
+
We believe for the vast majority of applications working against the older dynamices sdk libs, you should only need Microsoft.PowerPlatform.Dataverse.Client and Microsoft.Dynamics.Sdk.Messages.
57
58
58
-
If your working against CDS Only and or custom entities and sdk messages, you should only need Microsoft.Powerplatform.Cds.Client. If you do not experience that, or find missing messages in the CDS only scenarios, please let us know.
59
+
If your working against Dataverse Only and or custom entities and sdk messages, you should only need Microsoft.PowerPlatform.Dataverse.Client. If you do not experience that, or find missing messages in the Dataverse only scenarios, please let us know in the issues area.
59
60
60
61
61
-
<b>Note: Please be aware that during the Alpha \ Beta phases, these nuget packages are not supported via official channels.
62
+
<b>Note: Please be aware that during the Alpha \ Beta phases, these nuget packages are not supported via official channels.
62
63
Support is aware of them, however you will likely be directed back to the community forums for support during the Alpha \ Beta phases. A number of our dev's and PM's do monitor this channel and can respond to questions and feedback.
63
64
64
65
While we are monitoring the community forums, you are encouraged to open issue [here](https://github.com/microsoft/PowerPlatform-CdsServiceClient/issues)
0 commit comments