.Net Foundation Code Conversations, 15 Aug 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: .NET Core Plugin Architecture in the IIS Administration API with Jimmy Campbell

Description

Jimmy Campbell gives a tour of the IIS Administration API then shows how they implemented a plugin architecture in .NET Core.
Source code for this presentation:
https://github.com/microsoft/iis_administration

A

Hi. welcome to code conversations. today we're talking to jimmy campbell.. What are.

A

You going to show us jimmy?.

B

Today, we're going to be talking about the microsoft iis administration api., so it's a new rest based api that the iis.

B

Team is working on to allow consumers to completely configure iis over http, so.

B

You can use any kind of client, you want, the whether it be a mobile phone or.

B

Powershell or whatever you want and you can configure web servers so.

B

Things like creating a creating a web application, or... right, right, your websites,, your.

B

App pools,, all of your iis resources,. You can do that right. Here., awesome.,.

B

Since this is code conversations, I want to jump into some code today and I want to.

B

Kind of give a lay of the land of how somebody is going to start contributing.

B

To this repo, what maybe some things I might want to know. okay, cool.

B

So the microsoft iis administration api comes with this built in api explorer. You can.

B

See it on my screen right now, so every endpoint, that's exposed to the api, shows.

B

Up in this tool right here we have certificates files and the web server itself.

B

So any iis configuration is going to appear when I click on the web. Server.

B

So here we have endpoints for iis.. We see we have authentication, authorization,.

B

Application pools... all standard things that server administrators are going to.

B

Know are the bread and butter of what makes is great.

B

So this is all linked through.

A

And so I can click on this and I can see what the http response is that.

A

I'm going to get, and I make that call exactly so. This is really useful for.

B

Finding out what this api exposes cool on this tool right here and now for as.

B

Far as the architecture of the microsoft iis administration, api goes all these.

B

Links right here are plugins inside of the iis administration, application. okay.

B

So this is a .net core... asp.net core application. We have. We have one one main.

B

Dll, the microsoft is administration dll that bootstraps application loads. These.

B

Plugins such as the default document, plug-in, authentication, plug-in,, the authorization plug-in. and those plugins exposed.

B

Endpoints. okay., so they have their own controllers. Some even register.

B

Middleware, so it's it's a that's very interested and that's something I hear.

A

From people people ask like how do I do a plug-in based asking that application.

A

So that's really interesting to see you've done that right right, so the web.

B

Server plug-in itself exposes things regarding is that the main application.

B

Has no idea about run so controllers and things like that., so today I want to get.

B

Into the code, and just show exactly how we constructed this and how it, how it acts.

B

So this right here is the startup code for the ice administration api. This.

B

Is the main..., can you zoom in on that real quick? oh,? Yes, I can.

A

Perfect... or maybe a little bit more., I'm old. okay. there we go.. So here we have the.

B

Startup code for the ice administration api, it's just a regular asp.net core.

B

Application- and you see it right here- the it's doing what you would expect.

B

Sample code to do for asp.net core it has the configure services call and it.

B

Also has the configure call so that's where it's adding services and that's.

B

Where it's using the services that adds open container now, as far as our plug-in.

B

Model goes: you can see that when we start off, we load a module, json file, so.

B

This is going to be a text file which says all the plugins for iis... uh, for the.

B

Administration api, whether we want them to be loaded or they're disabled. What.

B

They are now we create a module loader using that modules json file, and then we.

B

Load them all, so we go to the definition of load here or actually tell you what.

B

Go to the module loader, so here's where it all happens, we call load module. We.

B

Pretty much scan for the plugins they're all dll's dropped into the product.

B

Folder we load them in., they all implement a startup type and the.

B

I'm module interface. So if I go to an example plug-in over.

B

Here you can see, this is a startup and it is extended from base module and base.

B

Model base module implements, I'm module, so the main application is going to load.

B

Microsoft, iis administration, web werver, dot, site,, get the startup class and then.

B

What it's going to do is treat it like it's own asp.net, core, application., oh,, wow!,.

B

It's going to allow it to add services, ok and it's going to allow it to use services.

B

So it's just you're on your own. It's like you, don't have to think about the.

B

Fact that you're a plugin., so you can register controllers and all that stuff. So from.

A

The point of view of somebody using like looking at this code like number one.

A

This is great for a plugin author if they wanted to create their own plugin.

A

It's not impossible to do yeah, so this approach is viable wherever so. The fact.

B

That is the main application has such a good model for registering and then.

B

Using you can definitely duplicate that in your plugins and if you just provide.

B

That interface, you can yeah absolutely do the same thing. We're doing also just.

B

Kind of duplicating that behavior cool so yeah, that's the general architecture.

B

Of how the administration api works., we have plugins all being loaded by one main application and as one last thing on our agenda, I just want to show that.

B

It's open, source., here's the repository right here and these are all the plugins.

B

And the main application just like I was talking about so if you want to go ahead.

B

And start contributing: here's where you get started.

A

All right, thanks. very cool. thanks a bunch.