📷 A modern, cross-platform, 2D Graphics library for .NET
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Anton Firszov df0361c212 finished README.md 9 years ago
..
Properties Initialized ImageSharp.Sandbox46.csproj 9 years ago
ImageSharp.Sandbox46.csproj added xunit.runner.visualstudio 9 years ago
README.md finished README.md 9 years ago
packages.config added xunit.runner.visualstudio 9 years ago

README.md

Purpose

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?

  • 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

NOTE: There was no Profile test option in my VS Professional. Maybe things were messed by VS2017 RC installation. This post suggests that you need Premium or Ultimate edition of Visual Studio to profile tests.

2. With JetBrains ReSharper Ultimate

  • Use the context menu from your test class Context Menu
  • Or Unit Test Exporer or Unit Test Sessions
  • When working with test classes, make sure you open them from the ImageSharp.Sandbox46 project!