search

VISHNULALR / aforge

Automatically exported from code.google.com/p/aforge
Other
0 stars 0 forks source link

Nuget package for Ximea [Aforge.Video.Ximea] dependency problem. #335

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Nuget install AForge.Video
2. Nuget install AForge.Video.Ximea
3.

What is the expected output? What do you see instead?
Expecting success, however, getting a problem because AForge.Video.Ximea 
depends on 2.2.4 of AForge.Video but no binding redirect included with in the 
nuget package.

What version of the product are you using?
2.5 of XImea via nuget, 

Please provide any additional information below.

Original issue reported on code.google.com by ericnewt...@gmail.com on 28 Feb 2013 at 1:24

GoogleCodeExporter commented 9 years ago 
Here's a screenshot when adding Nuget package in visual studio

Original comment by ericnewt...@gmail.com on 28 Feb 2013 at 1:30

Attachments:

GoogleCodeExporter commented 9 years ago 
Another wierd thing:
http://nuget.org/packages/AForge.Video.Ximea

returns 404...?

Original comment by ericnewt...@gmail.com on 28 Feb 2013 at 1:36

Attachments:

GoogleCodeExporter commented 9 years ago 
This is the build error:

------------
Assembly 'AForge.Video.Ximea, Version=2.5.0.0, Culture=neutral, 
PublicKeyToken=5cdcd64958730f99' uses 'AForge.Video, Version=2.5.3.0, 
Culture=neutral, PublicKeyToken=cbfb6e07d173c401' which has a higher version 
than referenced assembly 'AForge.Video, Version=2.2.4.0, Culture=neutral, 
PublicKeyToken=cbfb6e07d173c401'    
------------

Nuget dependency is to 2.2.4 of AForge.Video, but the actual dependency is 2.5.3

Original comment by ericnewt...@gmail.com on 28 Feb 2013 at 1:42

GoogleCodeExporter commented 9 years ago 
The package you are using is not an official package provided by AForge.NET 
Framework. You can see all official packages here:
https://nuget.org/profiles/aforge.net

The package you are referring to was created by "han6man". So all issues about 
his packages should be directed to him.

Original comment by andrew.k...@gmail.com on 28 Feb 2013 at 9:29