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 code won’t then compile, it will complain that it can’t find the namespace referenced in the using and it also won’t be able to find any of the objects that you reference in the class library. Took me a bit of figuring out but you need to open up the properties for the class library project, look at the conditional compilation symbols in the build tab (it might be something like ‘NETSTANDARD1_4’). You need to take this symbol and duplicate it in the build tab of the console application. You should now be able to rebuild your solution and if you have other code errors, etc the solution should now build.
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 . . .
The title pretty much says it all, there is no way to open an MVC2 project within Visual Studio 2012, there is no “auto-upgrade” path either! If you attempt to convert a solution containing an MVC2 project you will probably see the following error message: Subtype: ‘{F85E285D-A4E0-4152-9332-AB1D724D3325}’ is unsupported by this installation. If you do, then the only real solution appears to be graft the existing MVC2 project into an empty MVC3 or MVC4 project . . .