by bill-s, 2019-08-06T02:13:02.683Z
Join James Montemagno, Maddy Leger, and David Ortinau as they show you a glimpse into the future of building beautiful mobile apps with world class tools with Xamarin.
This session was recorded live at the Xamarin Developer Summit: July 11th-12th 2019 in Houston, TX. The Xamarin Developer Summit is a premiere community-run, cross-platform, mobile developer conference, to learn more head to https://xamarindevelopersummit.com/
by bill-s, 2019-08-06T02:08:41.828Z
This article discusses advanced Test-Driven Development (TDD) in C# through a simple example. Whether you are a new or experienced developer, this article will show you every step of TDD through a very simple example.
by bill-s, 2019-08-06T02:16:09.848Z
Approval Tests or Snapshot Tests are in my opinion a vital part of the testing ecosystem that can service a number of uses cases. In this post I’ll introduce the concepts and discuss some of the scenarios we may want to employ them to best effect.
by bill-s, 2019-08-06T02:16:24.548Z
Heap Sort, the second daughter of the family, has a busy life. As the owner of a local, well-liked restaurant, Heap Sort's Heaping Helpings, she is constantly running around trying to make her restaurant better. As the mom of four kids, she (and husband Cocktail Shaker Sort) are constantly trying to stay one step ahead of their childrens' antics, not always with success.
by bill-s, 2019-08-06T02:10:50.142Z
Recently, I’ve been asked if Roslyn can be used for helping with writing code that involves preparing mocks with NSubstitute. Of course, my answer was "Yes" but instead of rushing into creating a new project that would implement this functionality, I performed a small research. I checked nuget.org and Visual Studio extensions marketplace, and I discovered that there was a bunch of existing analyzers and extensions that facilitated working with mocks and not only for NSubstitute but for other mocking frameworks, just like Moq or Fake It Easy, too. In this blog post, I will show you how these tools are helping to avoid common problems with mocking and boost your productivity by saving you a lot of typing. Presented examples will be mostly based on the Moq library because it’s my favoring mocking package.
by bill-s, 2019-08-06T02:26:09.890Z
For some time now I’ve been a huge fan of using Dapper in both personal and commercial projects. With more and more projects lending themselves to Microservices architecture, or at the very least a large application being made up of many smaller components, Dapper just makes sense.
But I’m getting a little tired of telling the same story of what Dapper is and what it’s capable of doing, so here’s my attempt at a “crash course” in Dapper with .NET Core.
by bill-s, 2019-08-06T02:08:20.875Z
The ASP.NET team has built a command-line tool called HttpRepl. It lets you browse and invoke HTTP services in a similar way to working with files and folders. You give it a starting point (a base URL) and then you can execute commands like “dir” and “cd” to navigate your way around the API:
by bill-s, 2019-08-06T02:15:46.979Z
We would love to hear about your experience with building client applications in .NET. Your feedback will greatly help us to improve the .NET tooling and ensure our roadmap focuses on your needs. Participate in shaping the future of the .NET client development by taking this short survey (5 minutes to complete).
We are also searching for developers to discuss new concepts and prototypes, so tell us in the survey if you would like .NET engineering team to reach out to you about upcoming opportunities in .NET UI development.
by bill-s, 2019-08-06T02:12:33.572Z
In this episode (part 1 of 2), Robert is joined by Leslie Richardson, who shows several ways you can get the most out of Visual Studio's debugging tools. She shows a number of features, most of which have been in the product all along. Whether you are a new or experienced developer, you will see some things you can use to help solve issues in your code.
by kudchikarsk, 2019-08-05T17:35:27.210Z
Many of us were taught that .NET manages memory automatically. There is no need to explicitly free memory. It just kind of goes away with the garbage collector. Though, It doesn’t mean we can’t have memory leaks. In this tutorial we will learn what is a memory leak in C# and how to measure .NET application performance with a variety of tools to diagnose memory issues.
by ThomasArdal, 2019-08-06T08:12:56.593Z
This post is an overview of .NET tools I've built and a bit of history behind each tool. Learn more about the Web.config validator and XDT transform tester.
by bill-s, 2019-08-06T02:14:43.832Z
.NET Core 3.0 comes with support for self-contained executables. It means we can publish applications as a single executable for specified platform. Also trimming – removing of unused code from assemblies – is supported. This blog post demonstrates how to build self-contained executable using .NET Core 3.0.
by bill-s, 2019-08-06T02:21:33.361Z
Let’s say you are working in the kitchen and preparing a five-course meal. A five-course meal is a considerable amount of work, but fortunately, you have an assistant who can help you with the mise en place. You’ve asked your assistant to cube some Russet potatoes, julienne some baby carrots, and dice some red onions. After 15 minutes of working, you check on your assistant’s progress and ...
by bill-s, 2019-08-06T02:27:27.806Z
Single-page application (SPA) SEO is hard—not impossible. Read this resource-packed guide to optimize your React, Vue or Angular app for Google.
by bill-s, 2019-08-06T02:21:09.905Z
With the release of .NET Core 3.0 Preview 7, C# 8.0 is considered "feature complete". That means that the biggest feature of them all, Nullable Reference Types, is also locked down behavior-wise for the .NET Core release. It will continue to improve after C# 8.0, but it is now considered stable with the rest of C# 8.0.
At this time, our aim is to collect as much feedback about the process of adopting nullability as possible, catch any issues, and collect feedback on further improvements to the feature that we can do after .NET Core 3.0. This is one of the largest features ever built for C#, and although we’ve done our best to get things right, we need your help!
It is at this junction that we especially call upon .NET library authors to try out the feature and begin annotating your libraries. We’d love to hear your feedback and help resolve any issues you come across.
by bill-s, 2019-08-06T02:06:00.104Z
In this article we'll look into when it's helpful to use a code-behind in your Blazor development, how we benefit and what to expect when re-factoring existing components.
When working with Blazor the default component architecture is to have all of the markup and logic mixed within a single file (.razor). When components are simple this approach works well, however as the complexity becomes greater managing the entirety of a component as a whole becomes difficult. Using a "code-behind" approach allows for markup and logic to be separated into their own files. In this article we'll look into when it's helpful to use a code-behind, how we benefit and what to expect when re-factoring existing components.
by bill-s, 2019-08-06T02:15:28.171Z
It’s about two years ago that I announced .NET Standard 2.0. Since then we’ve been working hard to increase the set of .NET Standard-based libraries for .NET. This includes many of the BCL components, such as the Windows Compatibility Pack, but also other popular libraries, such as the JSON.NET, the Azure SDK, or the AWS SDK. In this blog post, I’ll share some thoughts and numbers about the .NET ecosystem and .NET Standard.