-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
[Question] Targeting .NET 7.0 Directly #254
Comments
FFmpeg.AutoGen has no dependency, so without writing some .NET 6 specific code it makes no sense to add .NET6 tfw. The result will be the same anyway. As far as I know when a package "A" targets netstandard, and it is using a package "B", which has netstandard and net6 version (and the net6 veresion is really contains some net6 improvements) it will use the netstandard version of "B". So in this case it makes sense to add net6 tfw to package "A", since it will inculde the net6 version of "B". But this is not the case with FFmpeg.AutoGen. Anyway I support adding net6+ target if there is a useful improvement in FFmpeg.AutoGen which needs net6+. |
@zgabi Yes, I'm talking about the case that an App or Package written in .NET6+ is targeting FFmpeg.Autogen. In this case (I think!) you will get much better performance if you use a .NET6+ FFmpeg.Autogen compiled dll. |
It is useful only when FFmpeg.Autogen takes advantage of the new features of .net 6. So changing only the tfw (without code modifiications, contitional compilations) makes no sense. |
.NET 7 has newer interop API - I am working now on adding .NET7 as another target platform. |
Hi @Ruslan-B, I was wondering if we could get better performance by compiling directly to .NET 6+ instead of just using .NET Standard.
I asked this in stackoverflow long time ago but I never got an answer.
The text was updated successfully, but these errors were encountered: