You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if you are interested in doing so, but you can modify the updated csproj files to build against multiple target frameworks and create a single NuGet package supporting all of them.
If you are interested in doing so, the changes needed in the csproj files to build against .NET 4.5.1, 4.6.2, and Net Standard 2.0 and create a single NuGet package are:
The full list of supported "Target Framework Moniker" is here
One advantage of this change (especially after doing the same to R.NET) is that developers wouldn't need to update the project to .NET 4.7 or newer to avoid adding all of the Net Standard DLLs to their compilation output (and to all installers, etc.).
The text was updated successfully, but these errors were encountered:
Thank you for this suggestion; I'll see if I can set this up soon. My understanding of targeting monikers is rather ad hoc and patchy as I use .NET less these days. I appreciate the help.
I don't know if you are interested in doing so, but you can modify the updated csproj files to build against multiple target frameworks and create a single NuGet package supporting all of them.
If you are interested in doing so, the changes needed in the csproj files to build against .NET 4.5.1, 4.6.2, and Net Standard 2.0 and create a single NuGet package are:
to
The full list of supported "Target Framework Moniker" is here
One advantage of this change (especially after doing the same to R.NET) is that developers wouldn't need to update the project to .NET 4.7 or newer to avoid adding all of the Net Standard DLLs to their compilation output (and to all installers, etc.).
The text was updated successfully, but these errors were encountered: