4Dotnet - DotnetFriday Meetup - 24 mei 2024

DotnetFriday is de beste manier om jouw weekend in te luiden! Het delen en opdoen van Microsoft .NET & Azure kennis mét een borrel en een hapje in de handen. Have fun with tech! De vorige edities waren uitverkocht, dus mis je kans niet en schrijf je snel in.

Toegang is gratis. Eten en drinken wordt verzorgd.

Let op: beperkt aantal plekken. Vol = vol.

Kom naar de meetup op vrijdag 24 mei 2024 te Nieuwegein.

Agenda:

16:30 - Inloop

17:00 - Niels Tanis | Using WebAssembly to run, extend, and secure your .NET application

18:00 - Dinerbuffet

19:00 - Stacy Cashmore | Azure Static Web Apps for the Enterprise

20:00 - Borrel: Drinks & Bites & Gezelligheid

Talks:

Niels Tanis | Using WebAssembly to run, extend, and secure your .NET application

WebAssembly (WASM) has come a long way since its first release in 2017. As a technology stack running inside the web browser, it even allows products like Adobe Photoshop to run in that context, and with Blazor WebAssembly .NET runs inside of the browser as well. Now, WASM is expanding beyond the browser to run in a server-based context. With the introduction of WebAssembly System Interface (WASI), the technology leverages a standardised API that allows it to run on any system that supports it, for example to support cloud-based workloads.

Had WASM and WASI been around in 2009, Docker would not have existed according to one of its founders, Solomon Hykes. WASM has a strong security posture given how it works with linear memory space and how it supports a sandboxed-based environment called “nano-process”, which uses a capabilities-based security model. Users can even take .NET and, with the help of WASI, run it on a Trusted Execution Environment (TEE) to add an additional layer of security.

In this session we’ll start out with going through some of the basic security features of WASM and then move to running and extending an .NET application it with WASM. After that we’ll focus on the security features and run .NET on a TEE and use the sandbox and the capabilities based security model to limit what it’s allowed to do.

Stacy Cashmore | Azure Static Web Apps for the Enterprise

Azure Static Web Apps. An easy way to get a hobby site into the world for very little cost. But that’s not all they can do! With a few changes to the out of the box experience, and using the standard, paid, tier we can use these Azure Resources in our enterprise architecture! We will touch upon infrastructure as code, to make reliable deployments to a known environment.

We’ll look into how to change the default pipeline to allow unit tests etc for the code, and deploying the same build applications into multiple environments. Finally, we’ll take a look at Custom Authentication - using Auth0 to authenticate and a custom Azure Function to provide the roles for our users.

Meld je snel aan, gratis toegang.

We vragen je om je aan de Code of Conduct te houden, deze vind je hier.