Skip to content

Commit 08c936b

Browse files
authored
Merge pull request #106 from microsoft/users/mbarbour/dataverserename
Rename CdsServiceClient to Dataverse ServiceClient
2 parents b9a74a6 + 03f60be commit 08c936b

File tree

83 files changed

+2025
-2067
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

83 files changed

+2025
-2067
lines changed

.gitignore

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,13 +40,14 @@ src/GeneralTools/PowerShell/Microsoft.Crm.SDKBuilder/Microsoft.Crm.SDKBuilder/v9
4040
TestResults
4141

4242

43-
#Visual Studio Files
43+
#Visual Studio Files user files
4444
/.vs/*
4545
/src/**/.vs/*
4646
/src/**/*.suo
4747
/src/**/*.vssscc
4848
/src/**/*.user
4949
/src/**/*.vspscc
50+
**/Properties/launchSettings.json
5051

5152
#Skip Nuget Packages
5253
/src/**/packages/*

README.md

Lines changed: 19 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,29 @@
1+
## NOTICE **Project renamed to Microsoft.PowerPlatform.Dataverse.Client.***
2+
3+
14
## Current Release Notes
25
Current release notes:
36

4-
[Microsoft.Powerplatform.Cds.Client](src/nuspecs/Microsoft.Powerplatform.Cds.Client.ReleaseNotes.txt)
7+
[Microsoft.PowerPlatform.Dataverse.Client](src/nuspecs/Microsoft.PowerPlatform.Dataverse.Client.ReleaseNotes.txt)
58

6-
[Microsoft.Powerplatform.Cds.Client.Dynamics](src/nuspecs/Microsoft.Powerplatform.Cds.Client.Dynamics.ReleaseNotes.txt)
9+
[Microsoft.PowerPlatform.Dataverse.Client.Dynamics](src/nuspecs/Microsoft.PowerPlatform.Dataverse.Client.Dynamics.ReleaseNotes.txt)
710

811
[Microsoft.Dynamics.Sdk.Messages](src/nuspecs/Microsoft.Dynamics.Sdk.Messages.ReleaseNotes.txt)
912

1013
## Overview
11-
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.
1215

1316
**IMPORTANT NOTE**
1417

15-
**The CdsServiceClient cannot be built outside of Microsoft**
18+
**The Dataverse ServiceClient cannot be built outside of Microsoft**
1619
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.
1720

18-
1921
This encompasses the contents of the following nuget packages:
2022

21-
[Microsoft.PowerPlatform.Cds.Client](https://www.nuget.org/packages/Microsoft.PowerPlatform.Cds.Client)
22-
-
23-
[Microsoft.PowerPlatform.Cds.Client.Dynamics](https://www.nuget.org/packages/Microsoft.PowerPlatform.Cds.Client.Dynamics)
24-
-
23+
[Microsoft.PowerPlatform.Dataverse.Client](https://www.nuget.org/packages/Microsoft.PowerPlatform.Dataverse.Client)
24+
25+
[Microsoft.PowerPlatform.Dataverse.Client.Dynamics](https://www.nuget.org/packages/Microsoft.PowerPlatform.Dataverse.Client.Dynamics)
26+
2527
[Microsoft.Dynamics.Sdk.Messages](https://www.nuget.org/packages/Microsoft.Dynamics.Sdk.Messages)
2628

2729

@@ -35,30 +37,29 @@ We are using this effort to for a few key things we have wanted to get done for
3537

3638
<b>We are currently in ALPHA.</b>
3739
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.
3941

4042
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.
4143

42-
At this time: (12/05/2020)
44+
At this time: (01/20/2021)
4345
The alpha version of the SDK libs supports the following and has the following notices:
4446

4547
* .net full framework 4.6.2, 4.7.2, 4.8 and .net core 3.0, 3.1
4648
* We now support all authentication types from CrmServiceClient, ( Client\Secret, Client\Cert, UID\PW Noninteractive, UID\PW interactive.)
4749
* 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 )
5152
* 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..
5253
* Plugin Development using this Client is NOT supported at this time.
5354

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.
5556

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.
5758

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.
5960

6061

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.
6263
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.
6364

6465
While we are monitoring the community forums, you are encouraged to open issue [here](https://github.com/microsoft/PowerPlatform-CdsServiceClient/issues)

src/Build.Common.standard.props

Lines changed: 0 additions & 14 deletions
This file was deleted.

0 commit comments

Comments
 (0)