© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
C#C
C#•3y ago•
10 replies
Kiel

✅ Making a library as accessible for different .NET versions as possible

I'm developing a simple library meant to be an API wrapper for .NET projects that might want to access it. I'd like it to be usable by as many versions of .NET as possible within reason. What should I target? should I target multiple versions? .NET Standard? I've seen some libraries use multi-targeting and then
#if
#if
blocks for newer-version features, so I guess that's a possibility too?

Or should I just not care and expect users to upgrade/update in order to encourage people not staying on ancient versions?
C# banner
C#Join
We are a programming server aimed at coders discussing everything related to C# (CSharp) and .NET.
61,871Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

❔ How to Package Multiple Versions of a Library Targeting Different Dependency Versions into a Nuget
C#CC# / help
3y ago
❔ Help with possible conflicts between different versions of a package
C#CC# / help
4y ago
❔ Install several .NET versions
C#CC# / help
4y ago
Modifier for a class you want as a base class only and making not accessible to external assemblies
C#CC# / help
2y ago