{"id":13102,"date":"2023-03-08T08:00:41","date_gmt":"2023-03-08T16:00:41","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=13102"},"modified":"2023-03-07T07:31:43","modified_gmt":"2023-03-07T15:31:43","slug":"microsoft-graph-net-sdk-v5-is-now-generally-available","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-net-sdk-v5-is-now-generally-available\/","title":{"rendered":"Microsoft Graph .NET SDK v5 is now generally available\u00a0"},"content":{"rendered":"

The Microsoft Graph .NET SDK v5, now generally available (GA), <\/b>allows you to take advantage of a fluent API and models that support retry handling, secure redirects, batching requests, large file management, and many more capabilities. F<\/span>ocus on what really matters, your business.\u00a0<\/span>\u00a0<\/span><\/p>\n

Along with all the features and improvements highlighted in the <\/span>v5 release candidate announcement<\/span><\/a>, such OData cast support and backing store, this GA release delivers a small change described below.<\/span>\u00a0<\/span><\/p>\n

OData cast now provides shorter names<\/span>\u00a0<\/span><\/h2>\n

Because OData cast allows downcasting the result to the right specialized type, v5 users now have access to all properties in the response, rather than pulling those out from the <\/span>AdditionalData<\/span><\/b>. To not require users to use the fully qualified name as a code path to cast, the OData cast was simplified to provide the shortest name possible when still avoiding collisions.<\/span>\u00a0<\/span><\/p>\n

https:\/\/gist.github.com\/maisarissi\/f9a6825cd51abc5128049af1b4a805fb<\/p>\n

For those using v5 preview versions, <\/span>the OData cast was shortened from <\/span>MicrosoftGraph<\/span><Entity> to Graph<Entity>. In the <\/span>example above, it changed from <\/span><\/span>MicrosoftGraphUser<\/span><\/span> to <\/span><\/span>GraphUser<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n

Methods doesn’t require full namespaces<\/span>\u00a0<\/span><\/h2>\n

As a similar approach to the OData cast, users now don’t need to specify the MicrosoftGraph namespace as part of the method. This change simplifies the fluentAPI by keeping only the method name as part of the method chaining.<\/span>\u00a0<\/span><\/p>\n

https:\/\/gist.github.com\/maisarissi\/68f10c40921fc872b9deed775d2580c2<\/p>\n

For those using previews versions of v5, the method was shortened from MicrosoftGraph<Method> to only <Method>, given the example above, it changed from <\/span>MicrosoftGraphSendMail<\/span><\/b> to <\/span>SendMail<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

Next steps<\/span>\u00a0<\/span><\/h2>\n

Check it out <\/span>this upgrade guide<\/span><\/a> to access a detailed document that outlines any breaking changes, fixes and will guide you through the migration that an SDK user might run while upgrading to v5 as well as provide examples for implementing the new features, helping you quickly take advantage of all the new capabilities.<\/span>\u00a0<\/span><\/p>\n

Add the new SDK to your project by running the following command in the Package Manager Console:<\/span>\u00a0<\/span><\/p>\n

Install-Package Microsoft.Graph<\/span>\u00a0<\/span><\/p>\n

Try out the new version today!<\/span>\u00a0<\/span><\/h2>\n

Try out the <\/span>new version<\/span><\/a> and let us know what you think\u202f<\/span>on GitHub<\/span><\/a>! For questions about the Microsoft Graph API, go to <\/span>Microsoft Q&A<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

Learn more about Microsoft Graph SDKs<\/span>\u00a0<\/span><\/h2>\n

The SDK includes a set of tools, libraries, and documentation that make it easy to get started building applications that take advantage of the rich data and insights available through Microsoft Graph API.<\/span><\/p>\n

Start saving time and removing complexity in your code today. <\/span>Sign up for the<\/span> Microsoft 365 Developer Program<\/span><\/a> to get a free Microsoft 365 developer subscription and start using <\/span>.NET to connect to Microsoft Graph<\/span><\/a>. We also recommend that you join our <\/span>Microsoft 365 Platform community<\/span><\/a> calls and events and get involved with other developers who use Microsoft Graph and build solutions for Microsoft 365.<\/span>\u00a0<\/span><\/p>\n

Here are some resources we have pulled together to help you get started.<\/span>\u00a0<\/span><\/p>\n