Microsoft 365 Community Microsoft Graph, 31 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction to Microsoft Graph .NET SDK v4

Description

In this 14-minute developer-focused demo, Microsoft presenters Maisa Rissi and Andrew Omondi educate viewers about a subset of new features delivered in the latest .NET SDK. Highlights include streamlined authentication with Azure Identity, added support for System.Text.Json, rich notifications that support encrypted content, and new Graph Response object. Also, ODataType is no longer specified by default, improved testability of GraphServiceClient and additional fixes. Visited code for authentication, serialization, Graph response, and PageIterator. This PnP Community demo is taken from the General Microsoft 365 Development Special Interest Group (SIG) - Bi-weekly sync call recorded on August 31, 2021.

Demo Presenters:
• Maisa Rissi (Microsoft)
• Andrew Omondi (Microsoft)

Supporting materials:
• Article - Microsoft Graph .NET SDK v4 now generally available with streamlined authentication and more | https://aka.ms/ga-dotnetv4
• Documentation - Get change notifications delivered in different ways | https://docs.microsoft.com/graph/change-notifications-delivery

Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos

A

Hi everyone, my name, is maizahisi and I am pm on microsoft, graph, developer experience team focus on graph fast case, I'm going to talk about the microsoft graph.net sdk, highlighting some of the new features and improvements in the v4 and andrew is going to be doing a demo for us to show how you can take advantage of these new features.

A

So we recently announced the general availability of v4 but to keep the speed short since we don't have an endless time here. We had select some major updates to highlight in this call, but we'll soon share the link to the blog post that contains all the information you might need.

A

So this new version of the sdk now takes advantage of the azure identity to improve the authentication experience, providing support for interactive browser, credential, which andrew is going to show in the demo in a few minutes and also client certificate, credential device code, credential and many others that you can find examples on how to quickly set up through the upgrade guide.

A

We also moved from newtonsoft.json to the system.text.json, since the last one is faster and serialization and deserialization.

A

This new library focuses primarily on performances, security and standards, compliance, so the sdk exposed the inbuilt serializer with the appropriate configuration.

A

So you can use this serialize object in this serialized object methods for serialization to you and this realization, from json microsoft graph allows apps to subscribe to change notifications for resources, saving the subscriber from having to call back to fetch the change resource so to provide a very uh better experience.

A

The sdk now includes native support for uh to decrypt the resource data inbreed notifications payload. So you can count on functions such as air tokens valid or the cryptosync to validate the token and the cryptic content in the notification payload.

A

We also did a bunch of cleaning uh so, for example, the sdk now also produced the graph response object, giving easier access to response information like headers and status codes, removing this information from the additional data property, allowing users to have a better experience and better performance during the deserialization of the response. Payload, the data type is no longer specified by default, so um preventing users from having to performance workarounds for some scenarios, where the api is not expecting this information.

A

So now the property is only set in cases where type integration is required. Still on the cleanup subject, the igraph service client interface has been removed. We know it has been used to build application tasks that depend on graph service client class by users.

A

However, these would cause code breaks whenever the microsoft graph metadata changes, making it less than ideal for mocking and inheriting thinking, only properties and methods of graph service client class have been made virtual, allowing mocking frameworks to overriding them, and last but not least, here are some of the major fixes included in this version. So beta and v1 libraries can now be used side by side in application.

A

The page iterator has been moved to the car library, making it accessible through both libraries and we added support to read stream responses in bad requests to support all these new features and improve the development experience provided by the sdk. The minimum version of the.net standard is now 2.0 and the dotnet framework bumped it to 4.6.2.

A

As I mentioned it before, you can access the blog post through aka.ms.ga.netv4.

A

To have access to detailed information about the net sdk v4 and find important links such as the upgrade guide, where you can see all the updates for this new version include those mentioned here and others and which improvements are considered as a break change and which are not so, let's get straight over to a demo. Now I hand to andrew and he's going to show you some of these new features. Take it away andrew.

B

Hey everyone yeah, my name is andrew and I'm a developer from the graph directs team. So I'm just going to spend some time to demo some of the stuff that we've been trying to add and release in the new version of the sdk.

B

The first thing I'm going to start talking about is uh really the the authentication so we've added support uh with, with regards to using our token credentials from the azure.identity packages. So typically someone who is working from the azure sdks world can typically use the token credentials and just plug them into the sdk, and that also makes the setup of everything uh way easier. uh Since uh it's you, don't really have to worry about the amps or configurations like in this scenario.

B

We want to do an integrative browser token acquisition and you would just pass in the client id into the options, create a interactive browser credential and then pass it over directly to the graph service client, and this would now help you be able to uh authenticate and uh be able to acquire tokens so like uh first, you quickly uh run this.

B

It would just like pop up the whole uh browser login window, and then I would be able to get back a graph service client that has the tokens are valid token for this uh yeah and now uh the next thing, maybe I would uh probably move on to- is to talk about uh the serialization and civilization work that we've done with regards to uh moving from neutron soft to system, to text to json, and uh a lot of that work is happening uh internally and we've noticed that a number of sdk users uh are did also have like a newton soft, uh specific code to to serialize and deserialize uh payloads, and with regards to that, we encourage guys to sort of like uh use the the wrapper methods and that we have exposed with regards to the serialized object and the deserialized object.

B

So using them directly uh will uh will create a serializer that is pre-configured to enable everyone to to be able to do the proper. Do the work in the correct way without having to worry about uh having to whether you've made the appropriate configurations with regards to sending data to the graph and back from the graph. So the other thing is really that the uh the the the properties in the additional data right now uh you will notice that they are now uh of of the type uh json element.

B

So I remember with neutron soft you would do like automatic casting and you would just cast the object to a string and what not, but since the json element from system.txt is really abstract and the whole boxing and boxing business gets a bit tricky, uh you would find yourself having to uh to write a statement like this to like sort of get the string out of the object in the uh in the additional data uh bug.

B

uh The other thing is uh the so the the thing is now. You won't find the headers and status information just as mesa had mentioned before, so that really is covered by the next uh feature that I was going to talk about, and this is with regards to the graph response.

B

So uh the graph response really is a way to help users have more power and more control over how they want to handle their responses and data from the graph. So traditionally you would find users and users, like you, are making a call to the graph with a statement that looks like this, where you would call the get a sync method so, with the graph response object, what we've done is uh for every uh get a sync method or poster sync method or uh updatersync method. We had.

B

We now have a another uh parallel method called like a get responsesync method, and what this does? It returns like a wrapper object uh and the wrapper object uh is what you call the graph response object and the graph response object will expose the headers, the the content and also the status code, and since this is now exposed when you decentralize, when you make the native call before with the gettersync, you won't necessarily find the header and the status info in the in the payload.

B

So and once you get the the the graph response object, you can now get the native object that you want like. In this scenario, you want the user from the from the user response object. You can call the get response, object or sync, and then it will now call the serializer and give you back uh the user object and with all this now, this enables you to uh to to make checks and write your code.

B

uh The way you want it because, or you can validate whether the status code is as you expected or not, uh and then the the other advantage is that uh you would find that, since you had like the status in for the status code info and the headline for in the additional data object, if you try to modify a property and try and try to post the same object back to the graph, that would throw errors, and that would force users every time they want to update something have to create a new object and post that.

B

But now, since there's no headers and uh headers and status code info in the in the object coming back, you can actually modify the same object and uh send it back to the api uh yeah uh yeah, so other than that. uh There are other things, as mrs mentioned, where you can use the pedigree to page iterator, both in core both in v1 and both in beta, and also we have sort of a lot of issues with regards to using uh v1 and beta in the same uh project uh yeah.

B

I think that's it for me.

C

Excellent ride on time as well, really cool to see the the great improvements uh to make it easier, and that's a really good point as well that you can use the same data object for updating information. So that's going to help a lot on making the code much cleaner and again just a reminder. It's the dps, akmsga.net v4 is the akms address for that one. So to get more details on it,.