SW Development: Visual Studio vs. Rider (IDE, TOOLS)

An article by the great and not late Mr. Peres (which you might have heard about before):
https://stackify.com/visual-studio-rider/

Citando:
"In the beginning there was Visual Studio. For many years, it was essentially the only tool that offered a comprehensive IDE with useful functionality that could be used for enterprise-level .NET development. Other tools existed, of course, but they were generally no match for Visual Studio.

In recent years, this landscape has somewhat changed: we now have Visual Studio Code, MonoDevelop, SharpDevelop and, more recently, JetBrains Rider. Not all of these are free or open source, and, in general, this shows up in the quality of the tool or the features it offers. This is not to say that open source does not offer high quality stuff – I have been an advocate of NHibernate for years – but only that companies that can spend money in having full time developers working on something usually benefit from that."

SW Testing | TOOLS: Continuous testing (in .Net)

http://www.dotnetcurry.com/aspnet/1396/continuous-testing-dotnet

Quoting:
"The idea of continuous testing is to make this feedback loop even more tight. The tests should be run automatically whenever the code changes and the developer should not need to run them manually. 

This can prove useful even if the developer only writes tests, after he has written the code under test. When he needs to refactor or enhance existing code, these tests will take on the role of regression tests, i.e. they will serve as a safety net from breaking original functionality.

However, continuous testing shows its real worth when the tests are written in advance or in parallel with the code under test, as required by Test Driven Development (TDD)."

Tools include:
"(...) three competing solutions available:

• NCrunch from Remco Software,
• DotCover by JetBrains, sold as a part of ReSharper Ultimate bundle, and...
• Smart Runner by Typemock, sold together with Typemock Isolator for .NET.

Microsoft’s first shy attempt in this field was a feature that was added to Test Explorer: Run Tests After Build switch made it possible to automatically run the tests after every build.

While this feature didn’t really allow for real continuous testing, it was nevertheless the first step in that direction. A full solution for continuous testing was introduced in Visual Studio 2017 as a feature named Live Unit Testing.

At about the same time, a similar feature was added to the command line tools for .NET Core. 

You can use the dotnet-watch file watcher (...)"

History: 2017-11-23: Update and reformatted

Bigdata, Hadoop and MS integrations

Some details on MS (.Net and Visual Studio) and Hadoop:
http://www.itproportal.com/features/the-integration-of-big-data-and-microsoft-net-for-software-development/

About Hadoop:
"Apache Hadoop ( /həˈduːp/) is an open-sourcesoftware framework used for distributed storage and processing of dataset of big data using the MapReduce programming model. It consists of computer clusters built from commodity hardware. All the modules in Hadoop are designed with a fundamental assumption that hardware failures are common occurrences and should be automatically handled by the framework."
Source: https://en.m.wikipedia.org/wiki/Apache_Hadoop

SW Construction: Typescript update

Typescript is JavaScript with "enhancements" (that attempts to avoid some JS "traps") from MS and there's a new Release Candidate available:
https://blogs.msdn.microsoft.com/typescript/2017/02/02/announcing-typescript-2-2-rc/