CodeX
Published in

CodeX

Dot Net library compatibility with Core and Framework

The challenges of compatibility with historical versions of Dot Net Framework

I’m very grateful that the .NET ecosystem is now properly open source. Prior to the introduction of DotNetCore, we lived with what is now known as the DotNet Framework —and there’s still lots of DotNet Framework software out there in the wild.

For those of us publishing software on NuGet, it’s worth spending some time making our software compatible with the DotNet Framework. Let’s investigate what it takes to set up a library compatible…

--

--

--

Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Spotify API —A Rite of Passage

weekly.tf — HashiConf Digital Videos (#14)

Node Twitter Sentiment Analyzer

Beyond the Source Code: Quines and Self-Replication

How To Setup CONNECT platform

WWDC21 in 5 minutes

Tutorials on Docker — Day 1

Places like Medium, which reward writers for their hard toil,

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ted Spence

Ted Spence

Software development management, focusing on analytics and effective programming techniques.

More from Medium

Quick tip — Local environment configuration for Asp.Net Core apps

3 Different Ways to Implement Value Object in C# 10

How does a middleware pipeline implementation look like?

How to return HTTP Forbidden in a .NET web API?