I’ve just installed MVC3.0 on a fresh PC using the new web installer application and was surprised at how long it seemed to be taking. Digging around a bit deeper I remembered that in the options I’d selected to use IIS rather than IIS Express and taking a quick look at the service panel highlighted that IIS was currently stopped. I restarted IIS and the MVC3.0 installation finished in seconds!
So if you’re having problems installing MVC3.0 then just take a moment to check that IIS is started.
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 . . .