Object oriented is one of the most broadly used programming paradigms. Problem is, most of the times, even if we use a primarily OO programming language, we’re not really taking advantage of it or other useful paradigms and language features, ending up in a mostly procedural scenario.

In this session, I’d like to share some ideas to improve our code, making it easier to understand and maintain, taking better advantage of our languages’ capabilities, mixing paradigms as appropriate.

None of these ideas are new, but it seems we keep forgetting them and get back to the same old mess.

Working as a consultant, something I often saw was teams moving from .NET Framework to .NET Core and .NET 5/6. As they adopted these new versions, they kept similar patterns and libraries. The teams weren’t taking full advantage of the improvements in .NET. One of those areas is Configuration.

Configuration holds our secrets, connection strings, application settings, and other data. We have checked it in, stored it in a web.config and transformed it in a pipeline. Today there are a variety of ways to configure our applications securely.

This session will cover:

• Strongly typed configuration
• Configuration providers – JSON, XML, INI files; Environment variables; Command Line;Azure App Config; Key Vault
• Dependency Injection
• The Options Pattern

What separates the highly-skilled developer from the one fresh out of college? Why is it that some developer’s code is far easier to maintain and others are nearly impossible to decipher? Both boil down fundamentally to whether you can easily understand the ideas and intent conveyed in their code. So what makes for easily understood code?

There are some communication principles we can apply to our code to make it cheaper to change, and faster to understand. After all Code is read more often than it is written. It ought to be easy to read!

.NET 6 takes us one step closer to the unified .NET platform where dogs and cats get along, Windows and Macs play nice together, and you can use .NET to develop for the Cloud, Mobile, Gaming, IoT, Desktop, AI, and the web. So, what’s included in this step? There’s a lot. Don’t worry. I’m here to guide you on this step.We’ll look at the following: 1) C# 10 language features 2) ASP.NET Changes 3) Maui, no, not the beach 4) Performance improvements 5) New APIs 6) Other enhancements We’ll wrap up the talk by looking at where we are on the journey to the unification of .NET. When the talk is over, if not during, you’ll want to download .NET and start using .NET to make your life as a developer easier.

Just about every developer who’s ever used Redis knows that it’s a blazingly fast in-memory data structure store. However, it’s traditionally had one major drawback, in order to access any data in Redis, you need to know exactly which key your data is stored in. This can make proper data modeling rather convoluted, but there’s good news. RediSearch, an Available Source Module of Redis, enables you to index, query, and aggregate over the objects you’ve stored in Redis. In this talk, we’ll talk about how to build indices, how to query objects stored in Redis, and how to aggregate the results of those queries, all using RediSearch and .NET.

Code coverage with quality unit tests are your first line of defense to reducing technical debt, increasing code quality and accelerating your ability to change and adapt code (without breaking it) while continuing to add new features. Most TDD sessions focus on the easy to test areas of your code base that are almost never what you experience getting back to your desk. Come learn why TDD is not a fancy practice for the coding elite, but an understandable, obtainable and practical approach to delivering value for every developer, and how, when done properly, will increase communication and design between the business stake holders and developers.

We will focus on practical steps to moving towards & embracing TDD. We’ll overview the normal roadblocks that people typically run in to, and practical coding strategies to overcome those road blocks on your way to embracing a Test Driven Development lifestyle – make coding without tests as uncomfortable as coding naked! – From the author of Automated Unit Tests chapter in the Wrox Book “Real World .NET, C# and Silverlight – Indispensable Experience from 15 MVPs, we will learn:

– Distinguish between the 4 major elements of automated unit tests. Code, Tests, Testing Framework and Test Runners and how they interact with each other to round out your engineering practices.
– Discover how Mocking Frameworks and DI make your tests easier to read and write in everyday life.
– Dig in to better ways to write and organize your tests so that they communicate intent, document your code for you and bridge the gap between development and business needs.
– We’ll take a more specific look at those “hard to reach” places like the edges of your code, extension methods and other interesting scenarios

Minimal APIs is new feature of .NET 6. We want to talk about integration of OpenTelemetry in Minimal APIs.

A fast-paced, demo-packed presentation highlighting new features in:

– Visual Studio 2022
– .NET 6
– C# 10
– ASP.NET Core 6
– EF Core 6
– .NET MAUI Preview

In a fast-moving software project, the demands that your application poses on its infrastructure might change often and drastically. Are you also fed up with having to apply infrastructure changes by hand? Not to worry! In Azure, there is the Azure Resource Manager, a unified API for managing all your Azure services in a declarative style, and a new more powerful templating language: Bicep!

In this session, Henry Been will give you a full tour of Bicep templates. Starting from scratch, we will explore how you can set up an architecture that is ready for deployment of your application code. We will touch upon syntax, manual deployment, and more advanced features as nesting templates, loops and conditions.

With the rise of Microsoft365 and Azure, the tech community has been given a plethora of both essential as well as powerful tools to excel in cloud development. With these, automation and cloud development are not restricted to just back-end development any more.

Instead, the cloud has enabled us to combine scripting languages, REST APIs and low-code editors in new and powerful ways that make more and more exciting solutions not only possible, but part of every-day coding life.

This session will explore how to combine e.g. Microsoft’s Graph API, SharePoint API and PowerShell in one environment (i.e. PowerAutomate) and what solutions can be achieved with this combination.

During this session, we’ll take a look at the proactivity tools that can be used to improve our development experience on Azure. We’ll talk about tools from multiple areas like storage, computation, automation, cleaning and many more. All of them are free to use, build by the Azure community or Microsoft to improve the cloud experience.

We will learn how to create a form in a Blazor app. The form will support built-in client-side validations with the help of data annotations. We will implement a custom client-side validator for the form. We will also add a custom form validator component for business logic validation along with the client-side validator.

You can see a GIF showing the app in action at https://www.syncfusion.com/blogs/wp-content/uploads/2021/07/Creating-a-Student-Registartion-Form-in-Blazor-WebAssembly.gif

Be it any industry, applications need to talk to each other. So, developers often build bridges – Application Programming Interfaces (API) – to allow one system to communicate to another. Over time, different API architectural styles have been released. Each of them has its own characteristics, patterns of data exchange, pros, and cons. REST, GraphQL and gRPC are three main options when it comes to API development and implementation In my session I will cover what REST, GraphQL, and gRPC are, all from a .NET perspective and give you a comprehensive comparison between them.

Developing cross-platform applications is complex. Some frameworks allow us to share the business logic layer. Some go further and allow us to share the UI layer, usually limited to the lowest common denominator. But even then – working with device hardware still requires not only error-prone platform-specific code but also developers familiar with each of the target platforms to maintain it.

What if there was a framework, which would allow you to write all your code in C#/XAML, with full styling and templating capabilities, with a single API to access device hardware? Meet the Uno Platform – your C#/XAML apps on Windows, Android, iOS, macOS, Linux, and WebAssembly!

Using the event sourcing support in the Marten library as a real world example, we’re going to look at strategies to handle potential concurrency issues within our server side applications. We’ll examine the usage of offline optimistic locking, serializable transactions, and very carefully use offline pessimistic locking.

Doing a deep dive into Marten’s asynchronous event projection processing, I’ll show some strategies for parallelizing work through the producer/consumer pattern. We’ll also examine how Marten parallelized work through data sharding, leader election, and work assignment throughout an application cluster. Just to make things harder, we’ll also talk about the necessary instrumentation and error handling it’s taken to keep all that parallel work synchronized in the face of intermittent errors.

If you listen to the 3 biggest players in the public cloud, they will all try and convince you that they are the “best choice” for moving to the cloud. However, they all have their idiosyncrasies and those may be the determining factor in deciding which provider makes the most sense for you and your systems.

In this session, we will go over those idiosyncrasies, what they mean to potential customers, and how they may affect onboarding and operations – all using real-world examples of where some things went well, and others not-so-well. We will also briefly cover hybrid clouds and how you can avoid putting all of your eggs into a single basket.