by dnwuQTLI06qsA, 2019-08-29T03:46:17.009Z
This is the second post in the series: Containerising Blazor Applications With Docker.
Part 1 - Containerising a Blazor Server App
Part 2 - Containerising a Blazor WebAssembly App (this post)
In part 1 of the series, we took a look Docker and some of its key concepts. Then we took the default template for a Blazor Server app and containerised it using Docker. In this post, we are going to take a look at doing the same thing but with a Blazor WebAssembly app.
by dnwuQTLI06qsA, 2019-08-29T03:45:36.765Z
by bill-s, 2019-08-29T04:05:49.790Z
I often wonder how to best decouple certain parts of an application. At first this seems pretty straightforward in the context of Vue.js applications. You have components and components pass down properties and emit events, that’s it. Right? Yeah, kinda. But also kinda not. Soon there will be the need to access global state or retrieve data from an external resource via an API. If we don’t be careful how we tackle these challenges, there will be the time when we realize that our components, which we planned to be nicely decoupled, use many external dependencies and are really anything but decoupled.
by dnwuQTLI06qsA, 2019-08-29T03:44:07.546Z
A few years back, I had given up on xUnit in favor of Fixie because of the flexibility that Fixie provides. The xUnit project is highly opinionated and geared strictly towards unit tests. It's great for that.
A broader testing strategy includes much more than just unit tests. With Fixie, I can implement any of the XUnit Test Patterns to implement a comprehensive automated test strategy (rather than, say, having different test frameworks for different kinds of tests).
In unit tests, each test method is highly isolated. In integration tests, this is usually not the case. Integration tests usually "touch" a lot more than a single class, and almost always, interact with other processes, files, and I/O. Unit tests are in-process, integration tests are out-of-process.
by dnwuQTLI06qsA, 2019-08-29T03:42:17.760Z
If you are building a data-driven web or mobile application, then key concerns you need to address is how data will be surfaced to the client and how the client can update the state on the server. This is not a new problem, and one that we have been solving for decades.
GraphQL provides one way to address this problem and uses an approach that provides significant benefits over previous RPC-based approaches. GraphQL was originally created at Facebook several years ago. It has been widely adopted since by Github, Concur, Airbnb and more. We’re even now adopting it at DocuSign. If you are doing React development, GraphQL has become the de-facto way to query from React clients.
by dnwuQTLI06qsA, 2019-08-29T03:46:55.716Z
This article is Part 2 in a 2-Part Series.
Part 1 - Refactoring to Data Driven Tests
Part 2 - This Article
The previous post was meant to be an encouragement and a warmup to data-driven testing. This post describes why I love this way of testing. Understanding a simple fact about testing moved me from “Oh, I should write tests” to “I want it all! And I want it now!” and Data-Driven Testing. And the simple truth is:
by dnwuQTLI06qsA, 2019-08-29T03:48:38.653Z
.NET Conf is a FREE, 3 day virtual developer event co-organized by the .NET community and Microsoft. This year .NET Core 3.0 will launch at .NET Conf 2019! Come celebrate and learn about the new release!
Learn more at => https://www.dotnetconf.net/
by andrea.angella, 2019-08-28T19:27:39.772Z
The Azure CLI is a command-line tool that provides a fantastic experience to work with Azure resources. In this episode, I share my first-time experience with it and how you can get started using it. It's definitely the best tool for the job!