erwinwolff/aforge

FFMPEG NuGet package lib built against wrong framework version

Closed this issue · 4 comments

What steps will reproduce the problem?
1. Create a .NET project building against framework v4.0
2. Include the NuGet package AForge.Video.FFMPEG.lib and its dependencies
3. Reference the VideoFileWriter in the code and try to build

What is the expected output? What do you see instead?

The project should build successfully, but instead it fails with the following 
message:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): 
warning MSB3274: The primary reference "AForge.Video.FFMPEG" could not be 
resolved because it was built against the ".NETFramework,Version=v4.5" 
framework. This is a higher version than the currently targeted framework 
".NETFramework,Version=v4.0".

It looks like the lib in the v4.0 folder in the NuGet package was mistakenly 
built against the 4.5 framework.

What version of the product are you using?

NuGet Id: AForge.Video.FFMPEG.lib
Version: 2.2.4.0


Please provide any additional information below.

Original issue reported on code.google.com by blachn...@gmail.com on 4 Jan 2013 at 1:56

I actually just tried the libs in net35 and net20, and I'm getting the same 
error. It looks like they may have been built against the 4.5 framework as well.

Original comment by blachn...@gmail.com on 4 Jan 2013 at 1:59

Why do you think this issue is an issue of AForge.NET framework? It seems like 
you do some custom builds yourself and to me it looks like either you have some 
issues in your build setup or there are some issues with NuGet. But so far it 
is not clear where is the AForge.NET framework's issue.

Original comment by andrew.k...@gmail.com on 4 Jan 2013 at 2:35

I see now that the NuGet package that I was using was not one created by 
"AForge.NET". It says that it was instead created by "han6man". I will switch 
to the ones created by "AForge.NET", although it looks like there is no 
official AForge.Video.FFMPEG NuGet package. 

To wrap up, you are correct, this was not an issue with AForge.NET. This issue 
should be closed. I'm sorry to waste your time, but thank you for your quick 
response.

Original comment by blachn...@gmail.com on 4 Jan 2013 at 2:42

OK, closing it then.

Original comment by andrew.k...@gmail.com on 4 Jan 2013 at 4:32

  • Changed state: Rejected