finished README.md

tests/ImageSharp.Sandbox46/README.md

@@ -1,12 +1,25 @@
 ## Purpose
-This project aims to workaround certain Visual Studio based .NET Core tooling issues of the time of it's creation (January 2017):
+This project aims to workaround certain .NET Core tooling issues in Visual Studio based developer workflow at the time of it's creation (January 2017):
 - .NET Core Performance profiling is not possible neither with Visual Studio nor with JetBrains profilers
 - JetBrains Unit Test explorer does not work with .NET Core projects
 
-## How does it work
+## How does it work?
 - By referencing .NET 4.5 dll-s created by net45 target's of ImageSharp projects. NOTE: These are not project references!
 - By including test classes (and utility classes) of the `ImageSharp.Tests` project using MSBUILD `<Link>`
 - Compiling `ImageSharp.Sandbox46` should trigger the compilation of ImageSharp subprojects using a manually defined solution dependencies
 
 ## How to profile unit tests
 
+#### 1. With Visual Studio 2015 Test Runner
+- **Do not** build `ImageSharp.Tests`
+- Build `ImageSharp.Sandbox46`
+- Use the [context menu in Test Explorer](https://adamprescott.net/2012/12/12/performance-profiling-for-unit-tests/)
+
+NOTE: 
+There was no *Profile test* option in my VS Professional. Maybe things were messed by VS2017 RC installation. [This post suggests](http://stackoverflow.com/questions/32034375/profiling-tests-in-visual-studio-community-2015) that you need Premium or Ultimate edition of Visual Studio to profile tests. 
+
+#### 2. With JetBrains ReSharper Ultimate
+- Use the [context menu](https://www.jetbrains.com/resharper/features/unit_testing.html) from your test class
+![Context Menu](https://www.jetbrains.com/resharper/features/screenshots/100/unit_testing_profiling.png)
+- Or Unit Test Exporer or Unit Test Sessions
+- When working with test classes, make sure you open them from the `ImageSharp.Sandbox46` project!