In steps 1 to 5, we opened the existing solution with the .NET Standard library and its accompanying .NET Core application. In step 10, we added a debugging point to the code. In step 11, we could see that it had stopped at the debugging point, at the .NET Standard 2.0 library itself. From then on, it performed like a normal debugging application. Visual Studio knew we were looking for code in the library.
In step 13, we moved the mouse pointer to the string parameter of the WriteLog() method, which is in the library code itself. Visual Studio showed us the value inside that parameter. Again, in step 13, we saw that we could jump to any area in the code we desired. This is a new feature in Visual Studio 2017. In step 15, we ...
