Event name: .NET Dominicana Monthly Event
Talk name: Tips for UI Handling in .NET MAUI
Language: Spanish
Date: April 18th, 2024
Link: https://www.youtube.com/watch?v=wqMLC4B1WA4
Thanks for reading!
Event name: .NET Dominicana Monthly Event
Talk name: Tips for UI Handling in .NET MAUI
Language: Spanish
Date: April 18th, 2024
Link: https://www.youtube.com/watch?v=wqMLC4B1WA4
Thanks for reading!
Within MassTransit, messages take the form of .NET types, which can be records, classes, or interfaces. Yet, these messages also carry their own distinct type. This video explores the diverse message types (or stereotypes, perhaps a more fitting term), such as commands, events, requests, and responses. I delve into when to employ each type and explain how these types are produced and/or consumed within MassTransit.
MassTransit
Documentation: https://masstransit.io/
Discord: https://discord.gg/rNpQgYn
Connect on Twitter:
https://twitter.com/phatboyg
Episode 799
Chris Nicholas on Enterprise Acceleration of AI
Chris Nicholas talks about how enterprises can use the power of AI to build useful solutions, what are examples of good use cases, and
Adventures serializing absolutely everything in C#
24 minutes by Isadora Sophia
Trim as many third-party dependencies as I can. Target native AOT when compiling games for web and consoles. Always stay on top of the latest .NET releases. Performance…?
Introducing the General Availability of MongoDB Provider for Entity Framework Core
sponsored by MongoDB
Unlock the full potential of MongoDB in your C# projects! The MongoDB Provider for EF Core is now generally available, enabling you to build modern applications with the EF Core APIs and design patterns you know and love. Discover how this integration can transform your development experience.
Critter Stack Improvements for Event Driven Architecture
7 minutes by Jeremy D. Miller
The feature set shown here has been a very long planned set of capabilities to truly extend the “Critter Stack” into the realm of supporting Event Driven Architecture approaches from soup to nuts.
Networking Programming with C# 12 and .NET 8
90 minutes by Chris Woodruff
We introduce you to the core concepts of network programming, guiding you through the essential terminology and principles that form the bedrock of all networked systems.
Some more C# 12
5 minutes by Tom Deseyn
In this article, we’ll take a look at some advanced features that part of the latest C# version: inline arrays, optional params and params in lambda expressions, ref readonly parameters, aliasing any type, and the UnsafeAccessorAttribute.
C# 13 Params Collections
5 minutes by Fons Sonnemans
In this blog I will explain the params Collection feature as documented in this proposal.
Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.
The following ebook reviews how your organization should think about how Copilot for Microsoft 365 can impact your organization’s modern working environment. It covers:
To start your journey with Copilot for Microsoft 365, being with this eBook. Download it below:
Doing the same thing repeatedly (and expecting--or hoping for--different results) is apparently a definition of madness.
That might be why trying to debug tests that sometimes fail can feel like it drives you mad.
It's a common problem: how do you know how much logging to have by default? Specifically when running automated tests or as part of a CI process.
Here's my answer:
Run with minimal logging and automatically retry with maximum logging verbosity if something fails.
It's not always easy to configure, but it has many benefits.
Not only does this help with transient issues, but it also helps provide more details to identify the cause of issues that aren't transient.
An issue is probably transient if it fails on the first run but passes on the second (with extra logging enabled.) It also helps identify issues that occur when no logging is configured. -- It can happen; ask me how I know. ;)
Be careful not to hide recurring transient errors. If errors can occur intermittently during testing and the reason is not known, what's to stop them from happening intermittently for end users, too?
Record that a test only passed on the second attempt, and raise a follow-up task to investigate why. Ideally, you want no transient errors or things that don't work when no logging is configured.
This doesn't just apply to tests.
It can also be applied to build logging verbosity.
You only really want (or rather need) verbose log output when something goes wrong. Such as a build failing...