.Net Conf 2020 Day 2

 Summary

Here are my notes on the sessions I attended for day 2.  There were many more I did not attend since the conference ran for 24 hours.

My goal for attending these sessions is to get get a high-level overview of the topic and see which ones I want/need to do a deeper drive on.

Day 2 Sessions

1. What's new in Visual Studio 2019

  • Customization
    • Themes
      • CRTL Q
      • Manage Extensions
      • Install Themes
      • After download, Close VS
      • To install
        • Ctrl Q Themes
        • Select the one you want
    • Project Templates
      • Create an existing Project as a Template
      • Export Template Wizard
      • Access New Template
        • File new project
        • Should show in the filter, but not always
    • Exclusive Filters
      • Allows you to filter out projects from your solution based only on the projects you want
      • Check the box on the bottom of the dialog
      • Right-click on only load the projects you want
    • File Nesting
      • Configure your own nesting rules
      • Right-click on section and select file nesting at that level
      • You define a rules file
  • Productivity Tools
    • IntelliCode Team Completions
      • Not shown
    • IntelliCode Suggestions
      • AI-assisted IntelliSense
      • Suggestions based on previous edits
      • Can apply the edit to other places in the file as well
    • Web Live View
      • In preview
      • Allows you to see you see changes live

2. HTTP API development with .Net, Azure, and Open API

  • OpenAPI => Swagger
  • On by default for web API
    • startup.cs
    • David Pine Comos Repro
    • Enable XmlDocComments
      • Includes templates
      • JSON and Ymal
    • Only turn on for Development environment
    • User the Name prop
  • New F5 experience for HTTP APIs
    • Goes to the index of the Swagger page
    • Mage it easier to do a POST
  • HTTPRepl
    • This is a NuGet package => CLI tool
    • Get the Microsoft one
    • You set Repal as the browser
    • Command-line REST client
    • Pretty powerful
    • Helps with API design
  • Azure API management
    • Integrate into Power Platform
    • Publish to API Management
    • Just Export to Power Apps
      • Power App custom connector
    • Connection Services Experience
      • Connects to Open API or gRPC

3. Accelerate .Net to Azure with Github Actions

  • Github Action => Ymal powered workflow linked to GitHub
  • Triggered by webhooks, schedule, or manual
    • Called "runners"
  • Actions generate logs
  • There is a community market place for actions
  • .Net - setup-dotnet
    • specific version
    • can use private packages
    • Have to use GitHub secret
  • Where to deploy
    • App services
      • Include server-side Blazor
      • Slots
    • Functions
      • Event-driven architecture
      • Can create from VS publish
    • Static Web Apps
      • Don't need a server
      • Blazor web assembly
      • Free SSL Certs
      • Add from Azure Portal
    • Kubernetes

4. Real-Time 3D games with .Net and Unity

  • Platform to create video games, 2d, and 3d
    • Support 20+ platforms
  • Big Community
  • A full suite of tools
  • Start in Unity Hub
  • Cool platform but complex
  • Good general overview
  • Does run on Mono
  • There is an asset store
    • Starter packages
    • Sprights
    • code
  • Build server
  • Unity Reflex
  • Microsoft game stack
  • aka.ms/unity101 => best place to start
  • There are multiple games engines available
    • Some written in .Net
      • MonoGame
      • Stride
      • Wave engine

5. Introducing new and improved Azure SDK for .Net

  • aka.ms/RichterCloudApps - Youtube
  • Guidelines
    • aka.ms/azsdk/guide
    • idiomatic
      • March the language of the SDK
    • Consistent
    • Approachable
    • Diagnosable
      • Enable you to self-correct
    • Dependable
  • Clients take endpoint and credentials
  • Clients have async and normal methods
  • The pipeline used to send the request to Azure is extensible
    • Contains client id
    • Clients handle retries
      • Same client id
      • Different logging
    • You can insert your own policies
    • Child clients inherent the options from the parent
    • The pipeline is immutable and thread-safe
  • 6. Secrectless development from local to cloud

  • This was mainly focused on Tye Project and Kerbenatics
  • Azure SDK was covered
    • aka.ms/AZSDK
  • Only keep your secrets Azure Key Vault
  • New Method => ChainedTokenCredential
  • You can even chain your own credentials
  • Look at the Azure SDK Blog for more information
  • Look at the git hub project "Memealyzer"
    • Cool project that crosses boundaries
    • UI is Blazor Web Assembly
  • New tool => AzurIte Table Review

7. Azure Data Studio Notebooks

  • This is a combination of tools
    • .Net Interactive
      • Really cool
      • Run .Net
      • Run SQL
    • Azure Data Studio
    • Vs Code
      • Available with insiders edition
      • Jupyter Notebooks
        • Executable code
        • Rich markup UI
      • Jupyter Views
      • SQL Magic
  • It is not fully completed yet
  • You will be able to turn any SQL file into a notebook
  • Really nice UI with data visualization

8. Secure DevOps with Identity

  • An overview was to stop putting secrets in clear text in-app settings or hardcoded in the app
  • Completely platform-independent or fully integrated into Azure
  • Set of libraries that just work
  • Don't use the settings file to store your configuration values
  • On startup pull your config from Azure key vault
    • You have to either use CLI Azure log in or Service Principle Account
  • You can use Azure Arc to set your local machine to be auth to the key vault
  • You can use a Linux VM as a git hub runner
  • Note that the new .Net 5.0 templates are using new Identity because Identity Server 4 team is going private


9. Get your JAM on

  • Use Blazor web assembly with Azure functions to build web apps
  • Deploy with GitHub actions to Azure static web site
    • Deploys both client and API via functions
  • Blazor template
    • AArronPowell/DotNetConf2020
      • Blazer Static Web site template
  • Downside
    • Only supports 3.1 for now
    • Auth not done yet

10. Setting Up Health Checks

  • Decide 
    • What to monitor
    • How often to monitor
    • Who to tell
    • Public / Private status
  • Adding a Health Check
    • AddHealthCheck in Config in start-up
  • Add SQL Health Check
    • ASP.NetCore.HealthCheck.SQlServer Nuget 
    • There is a package for MongoDB
  • Add Health Check for Azure Storage
    • Add NuGet Package
  • You can use tags to show subsets
  • You have to register your endpoints
    • Include tag if you want a subset
  • You can connect to a service like UptimeRobot or build your own
  • Can add Authentication
Today was a long day of sessions and I faded at the end.  I was hoping to view more today, but I will have to go back and view what I missed later.




Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchBox" 2. Created a new raz
Read more

Blazor Wizard Step Component

Image
 I like using step wizards in my applications, sign-up forms, shopping cart checkout, and complex data entry, but I had not been able to find a wizard step indicator that I liked so I built this one. As it turned out, it was not as hard as I thought it would have been.  There are a couple of key parts you have to keep in mind when using a step wizard, such as: 1. What step am I on? 2. Should the "Prev" / "Next" buttons be enabled or disabled on this step? 3. What kind of visual clues do I show the user? I will walk you through how we answer these questions in this sample project.   HTML The main container has a div that holds the progress divs, one div for each "step" of your process.  Below that we have our "Prev" and "Next" buttons We will need to wire in the on-click events for the two buttons.  The buttons will need to be able to be disabled and enabled via CSS class settings.           <div class="container">       
Read more