Today Jetbrains announced on their blog that they’ve released a resharper nuget package that will obtain project references via nuget, rather than making direct references to the locally installed code.
As we are currently in the early stages of transitioning from VS2008 to VS2012 we aren’t ready to start using NuGet(*) but I think I’ll be grabbing this plugin for when we do.
(*) In my last role we were using VS2010 and making heavy use of NuGet so can’t wait to get back into being able to use it 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 . . .