MicrosoftDynamics.Api 10.0.28

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package MicrosoftDynamics.Api --version 10.0.28
                    


                    

                
NuGet\Install-Package MicrosoftDynamics.Api -Version 10.0.28
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="MicrosoftDynamics.Api" Version="10.0.28" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="MicrosoftDynamics.Api" Version="10.0.28" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="MicrosoftDynamics.Api" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add MicrosoftDynamics.Api --version 10.0.28
                    


                    

                
#r "nuget: MicrosoftDynamics.Api, 10.0.28"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package MicrosoftDynamics.Api@10.0.28
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=MicrosoftDynamics.Api&version=10.0.28
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=MicrosoftDynamics.Api&version=10.0.28
                    


                            Install as a Cake Tool

License: MIT

Codacy Badge

MicrosoftDynamics.Api

A simple Microsoft Dynamics API nuget package using SimpleODataClient.

Nuget

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.37 37 9/1/2026
10.0.34 59 8/31/2026
10.0.28 163 8/21/2026
10.0.19 444 6/6/2026
10.0.18 280 4/16/2026
10.0.14 626 2/17/2026
10.0.10 562 12/17/2025
10.0.9 316 12/17/2025
10.0.7 309 12/16/2025
10.0.6 311 12/16/2025
10.0.5 304 12/16/2025
10.0.4 305 12/16/2025
10.0.3 302 12/16/2025
10.0.2 301 12/16/2025
2.0.25 2,017 1/5/2025
2.0.24 281 11/13/2024
2.0.19 756 6/6/2024
2.0.17 695 11/10/2023
2.0.15 574 7/13/2023
2.0.12 302 7/6/2023
Loading failed

Security fix: sensitive HTTP headers are now redacted in diagnostic output.

Previously the Authorization header, and therefore a usable access token, was written verbatim
into the exception message thrown for a failed request, and into Debug level request logging.
Any consumer capturing those messages retained usable credentials for the life of its log store.

Authorization, Proxy-Authorization, Cookie, Set-Cookie and common API key headers are now
redacted in both request and response headers. The authentication scheme and the credential
length are retained, so failures remain diagnosable without exposing the credential.

Breaking change to message text: headers in the failure exception message are now rendered as
"Name=value" rather than "Name: value". Code that parses that message will need updating.

Consumers should upgrade and then review existing logs for previously captured tokens.