Whilst working with VS2010 projects it can be really frustrating if you accidentally create your unit testing projects as class libraries (or migrate an existing class library into a unit testing library mainly because the context-sensitive “Add New” menu no longer contains the “New Test” option. This can be easily fixed by directly amending the project file, adding the following key to the main tag:
Reload the project in VS2010 and now your class library has become a testing library and you have “Add New Test” option(s) back again.
As part of his fantastic ‘What is .NET standard‘ presentation at DDD12, Adam Ralph provided an amazing amount of detail in such a short amount of time. One of the most valuable points, which is completely obvious when you think about it, is how you should work with .NET standard when creating libraries. NET standard now comes in a multitude of flavours: currently 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6 and 2.0. When starting out . . .
If you’re trying to access a class library (.NET Standard) from a traditional console application (in VS2017 those can be found under ‘Windows Classic Desktop’) you will run into problems; which can feel a little strange for something that was pretty simple in VS2015 and earlier. You can add a reference to the class library project (Resharper will even volunteer to add the dependency / namespace reference if you don’t already have it). But the . . .