Usually console applications are not associated with interactivity. Most of console apps accept some parameters via command line, do their job and exit. If the interactivity is needed, one has an option to build simple letters-controlled menu. While it is OK for simple applications, it is not enough for interactive applications. An alternative would be to create windowed application, which has richer keyboard and mouse control functionality out-of-the-box. But what to do if you want to stick with console application? Windows can enable your app to receive direct events related to mouse and keyboard sent to your console window.

If you are developing the Visual C++ apps, then probably you have stumbled upon the problem that appears once you try to transfer the app ato another computer. The app shows MSVCR100.DLL (or MSVCR71.DLL) not found error.

The app is fully wonrking on your computer, so thats quite confusing. Official Microsoft documentation suggests that you install special Visual C++ redistributable component. But there are lots of versions of this component: different architecture (x86 or x64), different Visual Studio versions. etc. Sometimes these components are conflicting with each other. One version is working with one program, but needs to be reinstalled to work with another program... Quite a mess!

Fortunately enough, there is a way to fix the MSVCR100.DLL missing error without the need to install runtime. But how is it possible?

If you are working in a multi-threaded environment, sooner or later you will stumble upon the situation with data corruption or exceptions due to unsynchronized access to common variables. For example, if you modify some member variable from two threads at the same time, there will be the so-called race conditions and the data may be inconsistent. To aid such a situation, you need to use an atomic lock object. The lock object in C# protects access to the variable from the different threads. Only one thread may access data at the same time.

Let's move to an example: