Microsoft 365 Community SharePoint, 10 Aug 2018

Previous Meeting

⏯

youtube image

►

From YouTube: Introduction to SharePoint Server 2019 Development Platform - August 2018

Description

Introduction to SharePoint 2019 Development Platform - Covering what's supported in the SharePoint 2019 Preview (and in RTM). Live demo on how to get started with SharePoint 2019 Preview from development platform perspective.

A

The second thing: what we wanted to talk about: that's that super cool to have the flow functionality for sharepoint online and all of that, but the one thing which which was also cool but because there's a lot of people still in on-premises and there's a lot of customers we're doing high print deployments, which is absolutely one of the key value propositions in Microsoft platform. So you can choose to keep some of your stuff in on-premise, some of your stuff in cloud and SharePoint.

A

2019 preview started on 24th of July, so we released a blog post in tech, community related on SharePoint 2019, that plug post and and the content, which was actually released. Didn't that much concentrate on what's available from the developer platform, and and now that I came back from vacation, I've been trying to address those gaps from a messaging perspective, because absolutely we need to address the developer platform.

A

Documentation side of the story as well, because there's a lot of people still doing even farm solutions and and which are absolutely 100% supported in the future as well. So for wrist. Part of the call we're gonna concentrate on the 2019 developer platform. I'm gonna do a live demo on this as well, but few slides. So how do we actually get started on SharePoint, 2019 preview? So, first of all, if you're interested on testing this, you need to download to 2019 preview I created a kms link for that one earlier today.

A

So a chemist's SP, dev preview that will point to the plot post, where this announcement was actually done. So the 2019 announcement that it's available in the blog post you'll find links to the DVD or ISO files, and also on the guidance files which, among other things, they actually contain the license to install the 2019 preview, because the Installer section asking the license ID when you're running through that. So you need to actually access those files. This is why they actually get started with this.

A

One is really to use a sure or whatever is your virtual machine platform. Whatever is your preference, obviously I use uh sure and because I I can really easily spin up my environments there now I'm gonna show you how what I did but technically quickly. Explaining did is then back in, like while ago, I created my SharePoint 2013 environment in Asher and I used other box templates, out-of-the-box templates, which are available in Microsoft Azure, which actually creates a separate ad machine as separate the sequel machine and a separate 7 2013 server.

A

So now what I did for 2019 is the data started a new 2019 server and associated that the same idea ad and the same sequel server so now I'm? Actually, then, in the same environment and I, didn't need to spin up the whole setup again and it's asking linked to SharePoint 2019 a km SSP 2019 preview. Underneath the first bullet point. That's where you can find links directly. There yes enable!

A

So whenever you have then run the in store, enabled or install SharePoint, when in 19 run the prereq run, the installers run the setup and configure thing not going to deep dive on what's actually happening there, but you need to enable the adding model so SharePoint framework. If you're planning to use the SharePoint framework in SharePoint 2019, you need to enable add-ins in the environment, and that means that you need to make sure that you have observers, application, enable and subscription settings service application.

A

If you are setting this by using the out-of-the-box helper resort and not using power shows, you need to actually still manually create the subscription settings service because that's not created by default by the automation.

A

This order, which is a pity I, don't know why and why somebody made the decision, but it is what it is and then you need to actually add an applicant main to the form, even though you would be using just SharePoint framework and not using apps and SharePoint framework doesn't actually use app domains and the reason why you need to do this is that SharePoint framework actually big. It backs on the add-in infrastructure, when you're deploying stuff and in the adding infrastructure.

A

It doesn't really understand that hey ooh you're, actually using SP pkt, well, not an app file. So there's no exceptions on that and that's why the ant in model has to be enabled, at least for now. Now then, you want to install versa, note and be mu and called the basic setters for sharepoint framework development, and you want to install SharePoint framework. One point four or one point four point: one there are some.

A

There might be some changes on this one we're still debating on the on the official final document guidance on this one, we're still in preview, how it's gonna add and in the preview timeframe, at least for me. The one point four point: one actually works perfectly well now: the and when you're actually creating a SharePoint framework solution, you need to choose a sharepoint online, only as the baseline option and that might seem slightly confusing.

A

But that's because in the sharepoint framework, when you're creating a solution, there's two options: are you targeting sharepoint 2016 or are you targeting went online and we don't have yet option for sharepoint 26 days, SharePoint 2019, so that's gonna be part of the SharePoint framework 1.6, which is scheduled to be out later this month. I'm gonna explain that in practice in a lifetime as well, but after this one we basically then have a SharePoint framework running in your form, and you can actually do extensions. You can do other stuff as well.

A

Now, if you are a ship on developer, you probably quite interested what is actually supported in SharePoint 2019, and this is now the status for preview. There might be some exceptions for this for RT M, but they will be really really small, so this is pretty much the status for go-live as well, so there will be obviously morning pages modern lists, big thing and modern pages. Modern experiences, modern sites, so modern team site without association to the group and communication aside, is included.

A

Modern sub-site will be there in GA right now in the preview version of SharePoint 2019, the modern sub-site isn't not actually exposed in the UI we are debating on giving you the workaround on that one.

A

You can actually because it works in the preview as well, but we'll give you the workaround in our documentation most likely later SharePoint framework, apps extensions and webparts absolutely supported web hooks supported as well as ad packaging is supported, and that means that if you create a shape on framework solution, you can just include JavaScript files and images inside of the SP pkg file and we'll host that for you from the App Catalog. So you don't have to worry about to see the end column, formatting and list column formatting. Is there ten on scope?

A

Deployment is available, so you're able to push web parts directly across your phone by adding them to their catalogue. Big thing as well and ALM ap is is available as well now, what's not available well before we actually own. The yes part still just do not avoid confuse anybody. Obviously, classic experience is still there form solutions is still there. Sandbox solutions still there feature framework still there, so all of the under stuff classic stuff. Absolutely there everything what you had in SharePoint 2016, pretty much is available in 2019 as well. Just to avoid any confusion.

A

Now, yes, question for Chris Chris is asking row: formatting is out. That is correct, because row formatting is not yet even released in SharePoint Online, so absolutely sample solutions technically still work in SharePoint 2019. But probably you shouldn't be doing that. So that's how kid.

A

Now is there a plan to allow one on sub sites in a long term shipment? Do you call yesterday implied it was no no I, don't know what is a SharePoint EU call, but that's wrong. Actually, we are looking into allowing modern subsides in a long term for shipment online and for on-premises as well, so sure we recommend people to have potentially individual sites in individual site collection that is more performant design and using hub sites in SharePoint Online now in on-premises, hub sites are not supported, so they didn't actually make that they.

A

They were released and sharepoint online slightly too late for getting them included in SharePoint 2019, and that's why hub sites are not available in 2019 and will not be there in GA site designs. Unfortunately, not there they're, not properties, not their modern themes are not there. This is actually slightly even slightly painful to be because the the out-of-the-box modern themes for modern sites and communication sites is there, but the capability for you to introduce a modern theme as an option is unfortunately not available. You can, however, use the classic. What is it look and feel?

A

What look? What is it? The classic theme capability, whatever it's called I can't remember: site collection, app, catalog might be actually there. It's pretty close. Thank you. Composite looks mentioned and ran on Windows and the site collection app catalog right now it doesn't work in preview. It might be there in GA we're looking into potentially making that happen as a hotfix in general, shape and framework third-party version will be one point four or one point four one, and this is still slightly debatable.

A

There is a pretty big difference, however, between one point, four and one point: four: one, because there's a difference between the node supported, node versions and ambient version, so we're trying to push it to the 1.41, but we haven't yet really locked the whole thing good and are we looking at few years without hub sites for own premises? Unfortunately, that seems to be an out the status we can't promise and put anywhere when there will be additional capabilities forum premises. Potentially there might at some point potentially there might not.

A

So don't quote me on saying that some of these capabilities will be released later they basically the hop sites went GA in SharePoint Online too late, comparing to the timelines of getting stuff included in SharePoint 2019, because we need to remember that SharePoint 2019 is based on SharePoint Online. The latest version is already in SharePoint Online. The the shipment 2019 is a fork from earlier this year from SharePoint Online, and then we clean up the the cloud dependent capabilities away, cool hypothesis before that.

A

Don't use that I think it's actually supported still I I, don't think we removed cross site publishing I personally always recommended people away from across I thought us into numerous reasons, but let's not actually concentrate and the now next steps for shippin 2019 development. So some things before I do the live demo as well, so the season, lookit and so client-side object model new kit for SharePoint 2019 I was planning to get it out before this call. Unfortunately, there was a unexpected certification thing: it would still need to figure out with new get people.

A

Eta right now is tomorrow, so you can actually then start doing development against. You have on 2019, what's actually kind of interesting, technically SharePoint 2016 see some new kit dust work with SharePoint 2019. What that's been missing, some of the capabilities which are available in 2019 I'm not going to deep dive on the versioning differences here. I might actually do that later in some of these calls and why that is, but let's not actually concentrate on that one in this one. Now shipment 2019 native support in SharePoint when it's a SharePoint framework 1.6.

A

So in SharePoint framework, one point: six, which is ETA by the end of August. There will be an option where you can actually target the code to be targeted on a shipment 2019 on words, including SharePoint Online. So, basically, you will have then three different options. When you run the Yeomen template and one of them will be then for 2020 19 API documentation updates ETA in September, so API season may be a server-side API updates. We unfortunately somehow magically didn't do this for SharePoint 2016 I.

A

Do not understand why so now we're fixing that for 2019, and so we are absolutely generating different documentation for done and other documentation will be then gradually introduced as well, so obviously highly dependent on what kind of feedback you as a community are giving us, because we have quite significant resourcing challenges on the documentation side of the website as well.

A

So we need to understand what is the highest demand on the on the documentation requirements now key guidance on SharePoint, 2013 or 7 2016 is 100% still valid, so feature framework, the classic form solution, development, all of the different those kind of things absolutely work and share 1 2019 as well. So we're not going to actually, let's say copy of that content.

A

We rather complement that content with the ship, an 2019, relevant stuff cool, a lot of stalking in a short timeframe, because I wanted to make sure that we have a time for a quick demo as well. So let me actually share my screen and let's see that we get stuff recorded and moving it is that screen.

A

And loading three dots I can see that somebody should be saying my screen. Somebody needs to confirm air one. Two, three, yes, exciting cool. So let's have a look on things.

A

So, first of all the how to get started on the preview is that if you write a kms M, a kms I'm, gonna, actually zoom in here a kms SB 2019 preview, that's gonna, actually land you on announcing availability on SharePoint, Server, 2019 preview, page from Bill beer, which concentrates on the enthuse okay abilities, and if we scroll down here, you can actually find the relevant download links and also what you need to have and also have a look on.

A

Is this reviewer guide and QuickStart guide, because this contains the licensing information or the license information for 2019? There was a question around guidance on upgrading from 2090 2016 to 2019, honest to be honest. I haven't checked on that at all, so I can't confirm or deny do we have guidance on that or not so simply haven't had a time to check that, but this basically gives you the preview version and you're able to then install that.

A

So, in my case, what I've done like explained, I actually have a 2013 environment with an azure ad sorry, ad sequel, server, provisioned at some point and then what I did was that I had just added my 2019 preview machine right next to that setup. So this way I'm just expanding my own premises. Environments on that setup well in this particular subscription, so I do have quite a few subscriptions, but this is my MSDN subscription, but technically that's how I added my 20:19 pretty easily available in usher for my VM environment.

A

So basically every one of you probably have your own way of doing this and that's absolutely fine, we'll anyway at guidance and article which is explaining how to get started sooner or later in our developer documentation as well. Now, let's see here's my actually SharePoint 2019 environment, so few things here. So what did I actually want to pinpoint so a few things from a service application site? So we get this one covered so in here, if you run the configuration this hurts.

A

So if we need one the SharePoint, 2019 installation, it actually asks you the configuration. We start to run as in one of the options when you start up now. Some of you might say, and all of the advanced people are saying that. Well, you should never ever use through this art, but if you're using this for development usage well, do these artists are in pretty decent job. So you don't actually have to wait our one, the power shells and all of that to configure everything it configures, your environment, pretty nicely only Jan.

A

It actually creates also that management service, so app management service application, but it does not create subscription service applications and that's something what you need to manually create using PowerShell, and this is something what we will absolutely include in our documentation. But you need to create this to your tenant as well to be able to open the framework in your SharePoint 2019 environment. The second thing: what you need to do in the form is configure, create def, catalog and also configure the app URLs, even though she upon framework doesn't use the app domain.

A

But these are pre requirements in the process and potentially will look into skipping this wide GA. So we'll see if we can actually get it fixed, but you need to do this for preview, at least after that's actually done. You are and then a basically ready for SharePoint framework development in general in SharePoint 2019. It is almost like SharePoint Online well in certain ways, so it looks like a shipment. Here's the SharePoint home, if I coded the.

A

If you, if I go to the app launcher, we can actually say that there's newsfeed still there's a one tribe link that SharePoint. So it looks like a SharePoint when one environment now in here I can absolutely then create sites. I can create a modern team sites. I can create modern communication sites depending again on your self-service site, collection creation or self-service site collection creation settings in this case, let's actually create a one site here, ccall demo- and this is a actually let's create a modern team site.

A

Community call demo and creating of these sites are obviously super fast, because these are modern sites, so want to treat this my site voila and that's pretty cool how fast it is comparing to the shipment when a six-day in a classic site, collection creation, which always takes quite a long time now, if I want to now do development on SharePoint framework development in here there are certain things of which we need to remember now.

A

First of all, let me actually create here this too. Oh, do I have anything here, no I, don't have anything here. So let me actually run the SharePoint at SharePoint. I can write into Microsoft SharePoint.

A

Sharepoint, so this one will start to SharePoint framework generator and there is like I just can't do this properly. So let me actually do this yo. This is always good. Yes, I'm always doing that mistake. Thank you David, but you can always start here if needed, because if you're lazy, you can just select the Microsoft SharePoint from here and then it's that's going to actually start this thing now, in my case, I've installed shipment framework.

A

One point for point: one to this environment: I'll show in a second which means that when I actually create the solution, I wanna target shipment online, even though that's slightly confusing, but the SharePoint 2016 onwards is for SharePoint 2016. That will actually create you ship one framework, 1.1 version of the environment, this one because I'm actually installed one point for point. One will create me. One point four point: one solution, so that's actually the right one.

A

For now, whenever we get the SharePoint framework, one point: six out, you will have a third version and third option in here which will be then SharePoint 2019 onwards in your clothing sharepoint online. So, in my case, I'm gonna actually quickly break this.

A

Let's see actually find the right keys from my keyboard. I'm still learning this keyboard no come on there we go so in my case. I do have a SharePoint framework, a shipment framework installed, but it's one point four point one and how did I get that installed? It's actually getting installed. So if you do installation- and all of this is absolutely getting documented- so if I do MPM, install Microsoft, SharePoint, generator and I add explicitly the right version in the end of this command. That will then install the one point.

A

Four point: one version for me. So that's how you actually target the specific version to be installed on this machine cool in my case, I've actually created a call extension just to show this one in practice and I do apologize will go vitally slightly long today, because I want to get this one documented as a video. So if I go call extension, that's my solution which I can actually see over there as well.

A

Let's actually do call up upon the ship, so I'm can actually make that solution, ready to get contributor and then do a call up.

A

One dollar package solution, so I'm not gonna, do deep parking or anything I'm kind of just show that it's working properly there we go bucket solution ship and there we go and then Explorer and let's open that one so I'm actually able to say that I just created a new version of the solution and in deists actually application customizer and what that means that we can actually now install this application customizer to our app catalog and there's certain things in preview which you might not actually well.

A

You need to be aware that or don't get, let's say fault. So, when I'm instant in this solution, it is using asset packaging. That's the packaging means that my JavaScript files and my images are automatically hosted by the phone. So you don't actually need to host this JavaScript files anywhere, which is pretty cool. So it's inside of the solution package almost like a almost like a sandbox solution, but not quite now what it means. Then it is that when I'm installing this, it's actually saying OOP.

A

So it's actually saying that the client-side solution will get content from following domains. And it's saying shipment online, which is highly confusing and that's a mistake because we just haven't actually considered on-premises in this dialogue, so it should say SharePoint form. So it's not actually copying anything on a sharepoint online. You don't have to have a shipment online.

A

Everything is from the on premises and one now clicking that is going to then install the solution and that's now available and now, if I go back to that site, which we just created, community called demo, site content and I've installed or or I have all of the capabilities available, I'm adding an end. I can actually see my stick called ml client-side solution available. That's now getting installed on the page and in any second, we can actually then see the extensions available and getting loaded on the side.

A

So, let's see one two, three one, two three still installing there's a timer job running behind off the scenes in the server and whenever the time a job has executed properly, we were able to see that the extension has been installed properly to the side. Now, what's also to just a pinpoint, is that this one? We do support the non scrub deployment, so you're able to use that one to go shred points by the way, Pavel's comments, app deployment has been taking some time lately. This is my own premises form.

A

So whatever has taken time, for you doesn't mean that it's taking time for me in my own premises form so that's a different setting. Now there we go there's my extension extension is getting rendered, it's a super cool header component and now seriously and a super cool and awesome filter, oh my god, but you can actually see that my extensions are getting rendered properly in the on-premises form, it's Chevron 2019 and things are working, but the tenant scope deployment like mentioned, supported you're able to push webparts available to all of the sides.

A

You're able to use that actually also together with the extensions. But then you need to enable the extension in a side by side level. One point still on the demo side of the story.

A

If I go to the sharepoint and really pinpoint this one, it is a pity and that we don't have a site designs available, which means that you can actually modify this selection and you can't actually modify what's happening with the communication sites or the team site creation, and that is a nasty limitation technically and if you need to run code whenever the communication side is created. That means that, well, I shouldn't probably say this out loud, but there's always an option of implementing a farm solution and using feature stapling, so not necessarily the optimal solution.

A

But then again it's on-premises farm solutions, absolutely supported. If you want, you can still use classic experiences, you don't have to use the modern. You can gradually introduce the modern, so there's multiple different options for you to take advantage. So we do not force only modern in shape. One 2019, but yes, I, mean I said it is different.

A

Everyone told me yesterday that you can't say that, but it is, if you have a business scenario, that you need to enable running code whenever a modern communication side is getting created, probably feature stapling is the only way to do that. Now, let me actually back on the slides and we can close up the call.