Just as I start getting up to speed with WF4.0 MSDN magazine publishes an article detailing what’s new in WF4.5. It looks like there’s a lot of good stuff coming but the main thing that I noticed was that v4.0 requires full-trust to run. That shouldn’t be a problem for the project we’re intending to run the workflow in, but if it will run in partial trust in the next release that will open up its usage for many other applications.
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 . . .