Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider multitargeting to take advantage of newer .NET performance #59

Open
lunarcloud opened this issue Nov 6, 2023 · 3 comments
Open

Comments

@lunarcloud
Copy link

https://learn.microsoft.com/en-us/nuget/create-packages/multiple-target-frameworks-project-file

<Project Sdk=”Microsoft.NET.Sdk”>
 <PropertyGroup>
 <TargetFrameworks>netstandard2.0;net6.0</TargetFrameworks>
 </PropertyGroup> 
</Project>

When you package it, both dlls end up in the nuget

@KevinBaselinesw
Copy link
Collaborator

thanks for the tip. I am not sure what the advantage is.

Do you think that .net6.0 will offer higher performance than .netstandard2.0?

@lunarcloud
Copy link
Author

lunarcloud commented Dec 13, 2023

Do you think that .net6.0 will offer higher performance than .netstandard2.0?

Yes, definitely it will improve the memory usage and performance at least slightly (probably more than)

@KevinBaselinesw
Copy link
Collaborator

I experimented with this when you first suggested it. I was able to build multiple versions of the library. But then I tried to use the new library in a test/performance app and got all sorts of link errors. You may have heard that I started a new job recently so I am pretty busy at the moment. When I get some free time maybe I will take another peak at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants