Rather, seeing it in action is the best way to make sense of it - at least that's how it worked for me. It's not a concept that comes naturally unless you've been following the evolution of. NET Standard seemed sort of academic.īut there's still a lot of confusion for people who are not keeping up with all the latest. NET Standard whereas in the early days of. With more implementations out in the wild now too, it's easier to see and realize the benefits of. Things have gotten a little clearer recently with better documentation from Microsoft and clearer designations on what versions of the various. The idea of targeting or consuming a library that is not really a library but a specification which in turn affects the build process and runtime binding takes a bit getting used to. NET Standard has been around long enough now that most people are reasonably familiar with this somewhat 'unnatural' concept.
0 Comments
Leave a Reply. |