Microsoft 365 Community Development, 11 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft 365 PnP – General M365 Developer SIG community call – 11th of June 2020

Description

June product releases: PnP CSOM Core library, PnP PowerShell, Modernization Scanner v2.12, yo Teams - 2.15.0-preview2. To be delivered within days: yo teams training package (8 getting started videos) and a video: "No code solution to expose SharePoint pages in Microsoft Teams as personal apps." There are no demos in this call, however Bert Jansen (Microsoft) @O365bert and Paolo Pialorsi (PiaSys) @paolopia delivered a brilliant introduction on the PnP Graph first library - a .NET based SDK that unites breath of Microsoft Graph with the depth of SharePoint REST. The host of this call was Vesa Juvonen (Microsoft) @vesajuvonen. Q&A takes place in chat throughout the call.

• See the full blog post for this call at: http://aka.ms/spdev-blog.
• Download invite for bi-weekly General M365 Dev SIG call: http://aka.ms/spdev-sig-call
• Learn more about the SharePoint developer community at: http://aka.ms/m365pnp
• Visit the SharePoint PnP Developer Community YouTube channel: https://aka.ms/spdev-videos

A

Welcome everybody: this is general Microsoft traces, the type of development special interest groups. It is why why we listen, it is June 11th 2020 and we do have a PC a busy busy busy agenda again, as we kind of talk about quick updates. One slide updates on the open source projects.

A

I have some news before that, one just to recap on where we are and what what's actually happening and some teasers which are coming pretty soon, and then we have three demos coming out so and we're trying to speed up again to intro in 15 minutes and then move to the demos to give them 15 minutes each.

A

Hopefully, we can figure out the technical issues which we seem to the experience and but let's see how this goes now, quick update on the opportunities to participate with the community not going to spend too much time in here trying to catch up. Is that? But key point here is the try to be active if you're interested on speaking in these sessions. Please let us know we do welcome any community members to do live demos in here so and showing your learning stand.

A

Whatever you're showing doesn't have to be open source, it might be learning based on a design or an approach which is taken, and please remember that be active in the key table and provide us feedback now.

A

This is all the assets and different locations, but we have this so many stuff happening, and the key point here to remember is that if you go a game, is entry is to 5 B & B, the last URL on the slides, and you can actually access all of this stuff, one single location, so you can find the symbol galleries. You can find the the initiatives, the projects and open source stuff and the videos from a one single location.

A

Now, if you're not super familiar with the key top and this and there's a growing interest on doing this- which is great- and it's awesome to see the interests in here and there's a lot of other people who are not super familiar with github either, and that means that we need to help you.

A

So there is no multiple, first time multiple training sessions coming in June at the first time, a contributor session related on the code and then the community doc sessions as well also contributing only as an articles these in the github or in the docs that Microsoft has gone. So if you're not super familiar with github, you want to get confident on. You know that we're doing these are instructor-led sessions.

A

Let my David Warner and Hugo Bernier to help you to learn how to use guitar so again, then time start contributing and open source and it not just only on our open source stuff, but in general github and that's really cool. So this is really really nice session, so non getting started on on this area.

A

Now this is a teaser which are gonna really is hopefully next week related on what, depending on a few timelines and resources resource discussions which we are having, we have two videos and the training purchased already pretty much ready to go, but we will release a really cool set of yo teams, training, videos, eight videos and basically covering all of the basics, on getting started on using your teams, and we have eight different MVPs.

A

Well, actually, Bob chairman is in Microsoft employee who have probably participated and created this video, so really cool set of videos are coming and they will be released in the YouTube channel. There will be a blog post, obviously announcing this one, hopefully Monday Tuesday Wednesday next week, so just the teaser and what's coming on this area of Microsoft themes, obviously being a big focus area and interest area in general, in Microsoft and whit's impacts, oh well, it impacts from us, but that's obviously pretty obvious.

A

It's not impacting we we built Microsoft themes, use it's true our channels as well, one also additional teaser related on that one. So this one I was planning to get it out already today, but it seems to be that it's going to be delayed until tomorrow and we will finally have an official statement, documentation and also video how to embed SharePoint pages and Microsoft teams, including all of the limitations.

A

We call them out and explain what has been supported, what is being not supported and in the documentation we'll do it in a way that it actually works in the mobile and in the desktop article, so desktop clients for teams. So you can actually start using the scenarios where we embed SharePoint modern portals directly in the Microsoft themes, which we know that people have been doing, but we explicitly now call out that to be supported as well, so really cool from a team sentient integration perspective I also wanted to spend really quickly.

A

To recap on this one, if you missed on Tuesday, we talked about the roadmap or BIOS a SharePoint framework. One point 11 coming quite soon plan to come out in early July right now, roughly. If we can get everything validated and there will be improved, Microsoft graph, API I see some dotnet standard coming so fully already as soon and potentially as next week, depending again on small technical nuances, which we need to figure out. So that's coming really really really soon as well.

A

The Microsoft themes is a big focus area for us in general and then more branding settings and the board also are coming as well. Now, let's go to the BMP, see some core library and let's see if birch can actually unmute himself well.

B

That's alright ABC, some core library. The June release is out what are the big changes, I think the pasta authentication manager which is now I disposable.

B

Why is this important if you're using authentication manager, especially in cloud scenarios like an azure functions, for example, and combined with requesting access tokens to Azure, ICS or as ready, then we kind of created a threat to invalidate the token know that threat never died, essentially leading up to like thousands of threads in your Asha function, which is eventually could kill the function, so it has been fixed, adjusted using with I disposable, then there's other improvements, especially on graph methods you might as new additions to methods, and the last one I want to kind of highlight here is- is probably a topic pages for context.

B

So, if you were well, if you in future, you will be able to kind of hear when she's got execute to export and import those pages. Like any other pages that we have in SharePoint Online and a ton of small changes, small figures have been done. Actually, there's a lots of things happened in this release here. Looking forward, there will be a v4, but actually let's skip that. I will talk about that in coming them of SSO. Let's just try to go to PowerShell.

B

Our shell like this is an amazing amazing number like for the customers that we have before we have 1 billion commented executions in May, like just gonna. Imagine that 1 billion powershell commandlets that were executed in a it's, this kind of crazy number.

B

That being said things to do in PowerShell. So there was a lot of refactoring and a lot of PRS were merged in this month. So I think the list went down from 30 plus PR stood 3 or 4. So that's a lot of organ and then big shout out. Thank you to Quincy almost so who.

C

A

B

A ton of work to kind of enable OSP us to be merged. There's too many individual fixes faster to really highlight all of them, because it's just a massive massive update that we did yep.

A

Yeah absolutely now, let's go to the modernization, tooling Burt! You can talk about this one as well. Yep.

B

June release with each transformation so detect that takes classic pages and builds model pages from that on actually no changes, no bugs no features needed so hold it there for the scanner we did list 2.12. Actually, yesterday, no mistake and day before, which have some improvements are going to work for when InfoPath reports and a new thing is like you yeah. Just when you create private channels and gives you get site collections, those site collections, that can be a ton of them and they're. They should not be scanned because they are modern, they're already nothing.

B

You don't want to update those. So we skip those and think it's kind of a bit of a maintenance. Lee is actually done at the point. 12 from users perspective pretty stable usage, so we see.

A

B

To ninety thousand pages being transformed a month, many publishing pages, but wiki page is catching up and, if you're still using dialog web pages, this will be one of the last times that, after you might be provide this bit, it will go away in July timeframe. So take action now, if you so Needham right.

A

The latest version of the of the yo teams is a 2.15 preview to, and things are evolving nicely at the May 20 2008 the best month ever so you can actually see the growth on the right sides and the cross keeps on skyrocketing also in tune, as well as out those 1922 downloads of teams and, first time, over ever more than four thousand generated projects in the in the last 90 days. So that's pretty cool from that perspective, so adoption is scrubbing on the on the team side.

A

Now, what's going to happen next, there's going to be two point, sixteen version and which will be a maintenance release on that one and then there's a a more significant changes coming into version tree. There's an ongoing discussions on that one in the key table.

A

If you are interested on helping- and they say obviously we're looking into people would be interested on helping improving the yo teams and the generator and testing and there's a there's already a a great set of issues tacked in Quito and Victoria's more than happy to help with their with questions on those. If you're interested on helping now, let's see if how this actually goes, we are sixty minutes into the call.

B

The topic that Paulo and I wanted to talk about is the peak or SDK. You might have heard this name before we really briefly mention it. We really didn't really talk a lot about it or demo it actually. So this will be the first demo if Paulo can actually get into a mutant and present with. Let's see now, first of all, why are we building a Pinta core.

A

B

There's the key name kind of spills: the beans means it's like is a library for you to use. Today we have yesterday we have pp size, coffee tree so and PowerShell v3, which our current highly used components and products. It's.

C

Literally, like.

B

Believe the commandlets thousands of actually 40,000 10s a month using P besides go so it's this massively being used, but these components are fairly old, meaning we start off the building those six seven years ago, VESA. huh So it's a long time ago, and now, with support of that standard, which is really really close, we can we will actually make P piece, a scone, PowerShell, again kind of cross-platform and we'll get like a little bit of a we staffed. But still it is like a very big monolithic set of components.

B

They have loved pieces cause a ton of dependencies, so you everyone has bumped into those DLL hell issues, because we reference a very old devel and you want something newer and then you get into conflicts, etc. It's not really easy to embed a modern development patterns like dependency injection, for example, so scarf quite hard and also quite hard to test in to refactor. But the reason why is because this has been kind of organically growing over like six years, there's a ton of good features that this is hard to maintain now dot.

B

That's five is also around the corner, so I think that the current plan GA for the.net 5, is November 10th. This year we should be like a unified net stack unifying the regular framework and all that core into one that's like which will work on any device any platform essentially including inside the browser, the bracing webassembly, so the pin P code as the gay. The reason why is because we really want to be ready for the 25 and give you something that really works nicely.

B

A modern dotnet based development on any device any platform, and it also give us a way to surely be slowly features and capabilities from PB s-- ice core into a new clean code base, because we it's just too much work to otherwise card refactoring, PB, s-- ASCO would be like a massive massive. What you can slowly with end up with a lot of old legacy stuff in there. So that's why we started kind of a from scratch, so whopper wise for h1 2020.

B

So still this month we are kind of focused on one shipping preview versions of the PP core SDK and we'll talk about that in a second, but we're not releasing it. Obviously, it's just preview were developing. It right now. First mention that that we are hoping to get see supported at standard or next week. Hopefully, let's see June timeframe, at least, which enables us for h2 of this calendar year to like a version bump of pin besides kokum PowerShell and ship them.

B

With that standard support, so we should have to kind of figure out how we worship it will be like a new package or will be kind of example, and the current IP, besides co uk package, also at the core version of the standard version of it. So some questions to answer, but but at least we definitely are committed to a ship in besides Kokam powershell, based on CC symbol and standards, which will then enable you to use it in your functions. V3, for example, cross-platform Linux machines whatever.

B

So it kind of broadens the perspective, and you see, scenarios for our core libraries. I went that long were people working on the PDP core has decay targeting as better v1, so this calendar year and then over time. People as capable get bigger will get more features and will kind of combine things so that they're older, let's say older, be besides core library will also use Pinta core as the gay for certain tasks. That's a bit of to evolution.

B

So those two will slowly but surely merge together at a certain point that, but we keep on having Boyd for a while and because we definitely want to keep supporting but especially pin beside school and partial articles are for shephard on premise: well, arrest the pentacle as the gate only target SharePoint Online. So.

C

B

Why we definitely keep their PP sighs co-op, our shell around, so so I talked about Bill. Why? But you might ask yourself like what this is. Actually, what is big because gay, what does it mean and and I tried to have frame it and in one sentence, is a donut base, SDK that unites the Debrett Microsoft graph, it's a depth of SharePoint rest.

B

So essentially you will get a development and API and a model, the main model where you can develop against and it will have all the SharePoint features that you are used to know today to have today from the Ida system or come from. Yes all shape and features.

B

Are there combined to it with all the graph features that are kind of circling around SharePoint, which are somehow related to SharePoint example, if I as a team site, the team side is also connected to a team, then yeah, it's really easy for you for you to do team operations at a new channel to your team at a depth of your team, etc, postmessage.

B

So these things are as easy as, for example, adding a new list and new column to the list, that's kind of the purpose and what we are aiming at a unified through with API with a domain model built for model and development acing by default. Think there is what else to say about it: yeah if you're we have previews ready available.

B

So if you want to look at the source code and try things out there, there's a kit of them a slash in P, slash, go SDK where you can start finding and digging around and the coding and reading about it because also documentation how to use it also. Definitely how to come through to it.

A

You know I've come.

B

To that in a second as well, but just looking at the questions first or anything that I need.

A

B

We can address all those section will be coming anything.

C

Aside here, maybe we try to share my screen and try to play the demo right.

B

Source as I see, yep samples.

C

B

One yeah: let's take this one, just to kind of.

B

Okay, thank you.

C

So, as you can see, the overall idea of the PMP Core SDK is to provide a modern experience to dotnet developers. That's why we decided to use the dependency injection model and, as you can see right here on line 35, we can configure a bunch of services. Some of them are custom services like a service for authentication, another one to get an object that we call PNP context, which will be somehow the evolution of what we were used to call the context in the season word.

C

But it is a bigger context because it can give you access not only to the sharepoint online part of the story, but also to the whole set of workloads that we have in officer c5 and through micro graph. As burt already said, the idea is to have a graph first library. So whenever you will execute any kind of request by default, we will try to use micro graph as the primary choice and we will fall back on the SharePoint rest.

C

Api is only if it will be needed, for example, because we are trying to access the property or functionality which is not yet available to micro graph. We can see that here we build through the dependency injection model, the host builder. Then we build the host and then we start the host and right after that, starting from line 18. We create a scope which is not mandatory, but in this demo we do that and using the context factor in PNP context factory.

C

We can easily create a PNP context to access a specific target site or team or group in micro 285, for example. Here we access it inside a modern tin site and by doing a context, web dot get a sink. As you can see, we have the asynchronous model. By default, we can get the web object, loading, the properties like title list and master page URL. Now, if you will make a request, for example, to get the title and the description of a site that will that request will go through micrograph.

C

If you will ask to get information like the master page URL, that one will require to go to the SharePoint REST API, as I said, the first option is always a micrograph, the one, but we also support internally to a flag which is, by default. True the capability to use the beta end point of micrograph if needed.

C

So if you are targeting any of the endpoints which will need to rely on micrograph beta, we will do it automatically for you switching from v1 to beta, and of course, if you don't want to do that, you can simply switch the default flag to false and we will just rely on graph v1 and SharePoint REST API.

C

The interesting part of the story is that in the backend we do all the request through batching, so we will make batch request targeting graph and batch request are getting SharePoint rest so that we can improve the quality of your application and of your code, and we can reduce the probability to get throttled by the api's, because we are leveraging the batching.

C

And also leverage a language integrated query model to use these library, so you can, for example, make a query link query for a list or for some of the lists. You can use some extension methods like the load and include that we created to let you retrieve all of the lists, including the items of those lists and under cover.

C

We will convert the link query into an actual query for deep back-end API, which will be again by default graph or rest as a fallback, and you can also use you can see your line 162 that we have some extension methods like we get by title, for example, so that we can somehow mimic the behavior and the code that we are already all used to use when we work with the season so that, even if this library will be completely based on graph and SharePoint rest from a developer experience and from a developer point of view, you can reuse the same model, the same syntax as before.

C

For example, when you make a get by title, you can also include some properties that you want to select through the open data. Query that will be executed in the backend for you and as such, it is, we think, a really powerful library which step-by-step, we will improve right now.

C

This is just a preview, as Bert already said, but the overall goal is to give you a library which will let you develop solution in any kind of platform like blaze or a speed of net core, and so on so forth, not only reading data, but now we will not begin to any single functionality, but you can also use this library to add new items, update items and do stuff like that, so you can fully interact with the Micra to c5 platform, starting most likely from SharePoint Online, but not only targeting SharePoint Online, but also Mike, so teams ensure Active, Directory and all the other work laws which are available.

C

I. Think that's enough, in my opinion, based on the context in which we are using the code from github. If you want to add something else, but of course feel free to I, think.

B

It was a question about contributing from a scenic Eli. I think we are a pretty early stage here, but we definitely would like to see contributors.

B

So don't everything I said we are an early start of this project and meaning that we don't have a lot of stuff in there yet so we need contributors for that. We actually focus our documentation initially on contributors. So if you go to the link here, you will find contribute documentation. Essentially, we try to explain how things work and how you as a contributor, can extend the models that we have and then just kind of giving you that that kind of getting started information so.

A

Here is the contribution documentation so yep.

B

That's the documentation and it kind of really explains into fairly much depth, actually uh how it works so like that I web, what does it mean? How you build it? What other object that we have? How do you add additional mobile classes?

B

You can have a look at things, also, just a good way to understand how you can build things and then definitely one thing to get feedback there as well. You feel this is good, not good DF other IDs feel free to. Let us know there, but this should help you get started. If you want to contribute now, I think it's important that we, if you really want to contribute that that you, let us know affront, ideally, especially if you want to add additional model classes.

B

So, for example, in a weird like Yannick Glanville, is working on adding content type and feel support very did a couple of PRS. It emerged thanks for that yeah like now. If it, if there's five people starting to work on something similar, then there would be like a shame. It would be kind of a pity of you get similar work. So if you want to contribute, maybe just reach out to us or create an issue in the issue, this saying, like yeah I, want to work on this particular area.

B

Then we can agree as a team on who does what so that we don't do overlapping work. Also, if you're trying to contribute and reading this documentation, you get like more than happy to to explain things get into a call with you.

A

Explain how it.

B

Works and help improve documentation. The end goal is that it. This is fairly clear for everyone contributing and.

A

That people can just.

B

Jump in and start contributing to this project now what are we looking for type of contributions? The main thing is extending the model, so SharePoint is pretty big. We only cope with a little part of it today, segment graph, we cover a fairly decent piece of the team's functionality. Building everything, so first big task is extending that also it becomes more feature-rich unusable.

B

There are other areas to contribute as well. For example, we want to automate things series, so if you're good at getup actions and want example right and a get up action that also generates this documentation.

B

When we push a new token, a new article update I would love to have that so so, there's an area around automation, packaging, that's the zoo where you can contribute samples, definitely samples, so we're like using the library in blazes, for example, would be a really cool example to see the gloss weaker Tommy showed blazer in action already, but having like this library being used somewhere, pretty cool or on a mobile application, and everyone app service over a student that cohab your model, dotnet development samples for where this can be integrated.

B

So we're looking for those.

B

Documentation updates testing, we have a really cool testing system and follow you think you can agree on that, so we have like already like 170 test cases. We actually wanted to show that in the demo, but we count today, which is a pity. Actually, that's again, you click on load by TSS, yep yeah, alright. So this is an old screenshot, but today we F like one of them a 70 test cases and they run in around five seconds. On my machine.

B

We have an offline concept, so we have a custom kind of walking concept where you can do it a live test, and then we record the response and then later on, that test will be saved with the response. So like server side, if you commit today, if you push a change or do a PR, you will see that we automatically run all test cases against your PR in offline mode using that response file. So that also allows us developer to refactor things without the risk of breaking things, because she, the test cases, will really help.

B

You were keep quality high.

C

And let me saber that we also, let me say, a requirement that any any new contribution willing also include the tests so that we can easily and with an automated model, test new functionalities, new contributions and keep the library solid and fully available to the people using it. So the idea we have in our mind that, right now, every single new functionality will have a full testability. That's the idea, correct.

B

Correct so today we are at 80% plus test coverage, and we aim to get higher and to reach that bar each contributions have to also improve test cases. Now, if you find it how to write the test case again more than happy to help, explain things and show how things work, there is slowly for everyone on this, and also again definitely wanting to listen to feedback good ideas around multiple developments.

B

We did our best that there's always other good ideas out there and patterns that can be used so feel free to just reach out to us, and let us know using.

C

B

List or David communication anything will work.

A

Covering what we're planning to do with the PMP Core, the craft first API is really really cool as well. We'll get this one and this recording out anyway and within 24 hours, because I've been able to record my screen locally, so that will be available in the Microsoft 365 and sharepoint community be a big youtube channel within 24 hours. The next entry is through our general dev code will be in June, 25th and we'll schedule.

A

Some of the plan, demos from here the death call, let's see what what works for Stephane and Irving and then the next year plan framework aura is a week from now in 18th. The next monthly community call is in July 14th in general. We have a lot of community calls available if you're interested in joining this and joined some of them and based on your availability and interest.

A

All of these community calls are recorded and looking into actually splitting all of the demos in this community calls in the air more and more as an individual demo. So you can amore easily find the interesting bits and pieces for you, rather than being forced to join on all of the ghosts. In the case, you are actually finding something useful again. We do apologize. The technical issues we've been having this week if you joined on the Tuesday's, calls the monthly community call.

A

The recording of that call is actually super clean, so go to the YouTube channel check out the recording. It actually demonstrates nicely. What are we planning to do with the modern SharePoint search, and it also talks about the timelines related on that one as well so really cool stuff from that perspective, but thank you for this one, if there's in general feedback or input, but you want to share please reach out in social media and let us know now your input. This super super important and obviously the input of please fix the Mike's of teams.

A

We heard about that one. Yes, we're working on it. So hopefully this was one-time exception or one-time week within this year, when we are having these issues, but have a great rest of the week and we'll be definitely in touch cheers. Everybody bye, bye.