Switching Between .NET Core SDK Versions

In this article, we’ll learn how we can switch between the versions of the .NET Core SDK as per our needs.
If you have worked on one project that used .NET Core version 2.1 and then you installed .NET Core 3.0 Preview, you will get an SDK error while trying to run your .NET Core 2.1 project. This is because your current SDK version has changed to 3.0

Link: https://dzone.com/articles/switching-between-net-core-sdk-versions?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Automated Cross-Browser Testing

Testing a website in a single browser using automation script is a clean and simple way to accelerate your testing. With a single click, you can test your website for all possible errors without manually clicking and navigating to web pages. It’s a modern marvel of software ingenuity that saves hours of manual time and accelerates productivity. However, for all this magic to happen, you would need to build your automation script first.
In a previous post, we focused on setting up a complete test suite environment for running selenium scripts. But that script had a major drawback. That setup was focused on testing on only a single browser. Cross-browser compatibility testing is a major pain point for all testers and it’s also a major test case for all functionality testing cycles.

Link: https://dzone.com/articles/automated-cross-browser-testing?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Mobile-Orientated Architecture (MOA)

Update From the (Near) Future
This post was written looking back from the future of the 2020s, making some assumptions about what kinds of changes we’d see in tech and the progress of the Kotlin ecosystem. Well, it’s been almost a year, and so far our timing looks pretty good. Kotlin Multiplatform is entering production. Mutiplatform libraries are being released. We, Touchlab, have completely shifted gears from Doppl, referenced below, and are fully committed to a Kotlin Multiplatform future.
Last year, MOA and Kotlin were a little speculative. A year later, it is happening. The time to take a deeper look is now.

Link: https://dzone.com/articles/mobile-orientated-architecture-moa?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Use Higher-Order Components in React

In JavaScript, we have higher-order functions (HOC), which are basically functions that accept functions. In React, higher-order components are basically functions which accept component as parameters, inject or modify their props, and return a modified component.
Real world use case: Suppose you have a button that you want to be rendered with two different styles. Using the main ideas behind HOC we do not need to create two buttons with different styles, but, rather, create a single button component and pass it through a wrapper function that modifies its props or styles and returns a new component.

Link: https://dzone.com/articles/react-higher-order-components?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Create an Angular 7/ASP.NET Core 2.2 Application and Push it to Azure

Implementing the full CI/CD cycle on an Angular/ASP.NET Core application is not easy. Some digging and experimentation is necessary to make everything work. The goal of this article is to pinpoint the different steps and tricks.
The source code is available on GitHub: devpro/aspnetcore-angular-sample. There will also be links to the live demo, as well as the build and deployment pipelines.

Link: https://dzone.com/articles/create-an-angular-7-aspnet-core-22-application-and?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Enable Column Hiding in Ignite UI for Angular Grid

Ignite UI for Angular Grid is the fastest Angular Grid out there. It does not only run fast, it is also very easy to use igxGrid in your application. Ignite UI for the Angular Grid component class is named igxGrid and, on the template, it can be used as </igx-grid>.
In this blog post, let’s learn how Column Hiding can be enabled in IgniteUI for Angular Grid.  

Link: https://dzone.com/articles/how-to-enable-column-hiding-in-ignite-ui-for-angul?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Implement Pagination in an ASP.NET Core App

When you have to show hundreds or thousands of records on your web page then you should apply pagination. This is because your users must not see all the records on the same page (which looks bad), instead, they move from one page to another page, and only see the records of the selected page.
Pagination brings cleanliness in your web page. It is an important technique which you should never miss to use. In this tutorial, I will teach you how to create pagination in Records in ASP.NET Core.

Link: https://dzone.com/articles/create-pagination-in-records-in-aspnet-core?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Using Node 11.7 Worker Threads With RxJS Observable

With the release of Node 11.7, the worker_threads module becomes a standard feature and is no longer hidden behind the –experimental-worker switch. The worker_threads module allows developers to run JavaScript asynchronously in light-weight, isolated threads contained within the main Node process. This article will be focusing on how use worker threads to execute a task asynchronously and stream data from that task back to the rest of your Node application using RxJS Observables.
Before we get started, if you want to learn more about worker threads and why you might want to use them, I would recommend reading Node.js multithreading: What are Worker Threads and why do they matter? by Alberto Gimeno. Alberto has done a fantastic job explaining the purpose of the worker_thread module, provided some solid examples of where it makes sense to use it, as well as demonstrated some alternate ways to build a multi-threaded Node app.

Link: https://dzone.com/articles/using-node-117-worker-threads-with-rxjs-observable?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Several Years Later: A Case of the Telephone Game

Remember the Telephone Game? 
You can read all about it here, but the gist is the first person is whispered a message. That person then whispers the same message (to the best of their recollection) to another person. The process continues until the last person receives the message. At that point, the last person announces the message for all to hear. The fun part of this game is to hear how much the story changes as the message is passed from person to person.

Link: https://dzone.com/articles/several-years-later-a-case-of-the-telehpone-game?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Integrate WordPress API in React Native

As I’m wrapping up one of my projects (a React Native WordPress app), I realized that many React Native developers will face the task of integrating WordPress’s REST API with React Native, so I decided to publish my findings. Hopefully, this will help out developers who are making their React Native apps using WordPress as a backend. To be clear, I don’t recommend using WordPress as a backend for your mobile apps, but it comes in handy if you already have a blog or a WooCommerce store running on WordPress.
As you already know, WordPress comes with a REST API out of the box. If you don’t believe me, just check out this link, which returns a paginated JSON response with all posts of my blog. I swear I only installed WordPress and did not do anything else. Try out the exact same URL, but for your blog, and you’ll see your own posts.

Link: https://dzone.com/articles/how-to-integrate-wordpress-api-in-react-native?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev