search

jacobbo / WebEye

WebEye is a collection of .NET controls.
190 stars 132 forks source link

Reference not found when installing the nuget package #69

Closed marekside closed 4 years ago

marekside commented 4 years ago

Installing the package I'm experiencing the following issue, the package is installed correctly but the reference is not being added (PackageReference works correctly but for us it's unusable):

PM> Install-Package WebEye.Controls.Wpf.StreamPlayerControl -Version 1.0.6 Attempting to gather dependency information for multiple packages with respect to project 'ProofOfConceptWpf', targeting '.NETFramework,Version=v4.7.2' Gathering dependency information took 877.66 ms Attempting to resolve dependencies for multiple packages. Resolving dependency information took 0 ms Resolving actions install multiple packages Retrieving package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from 'nuget.org'. Removed package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from 'packages.config' Successfully uninstalled 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from ProofOfConceptWpf Package 'WebEye.Controls.Wpf.StreamPlayerControl.1.0.6' already exists in folder 'D:\TFS\Prototyping\Main\Client\WebEyeProofOfConcept_1.0.5\packages' Install failed. Rolling back... Package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' does not exist in project 'ProofOfConceptWpf' Package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' already exists in folder 'D:\TFS\Prototyping\Main\Client\WebEyeProofOfConcept_1.0.5\packages' Added package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' to 'packages.config' Executing nuget actions took 3.01 sec Update-Package : Failed to add reference to 'WebEye.Controls.Wpf.StreamPlayerControl'. Error HRESULT E_FAIL has been returned from a call to a COM component. At line:1 char:1

Time Elapsed: 00:00:04.3360130

jacobbo commented 4 years ago

Never heard about such an issue. Other nuget packages work well?

On Tue, 17 Dec 2019 at 09:28, marekside notifications@github.com wrote:

Installing the package I'm experiencing the following issue, the package is installed correctly but the reference is not being added (PackageReference works correctly but for us it's unusable):

PM> Install-Package WebEye.Controls.Wpf.StreamPlayerControl -Version 1.0.6 Attempting to gather dependency information for multiple packages with respect to project 'ProofOfConceptWpf', targeting '.NETFramework,Version=v4.7.2' Gathering dependency information took 877.66 ms Attempting to resolve dependencies for multiple packages. Resolving dependency information took 0 ms Resolving actions install multiple packages Retrieving package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from ' nuget.org'. Removed package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from 'packages.config' Successfully uninstalled 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' from ProofOfConceptWpf Package 'WebEye.Controls.Wpf.StreamPlayerControl.1.0.6' already exists in folder 'D:\TFS\Prototyping\Main\Client\WebEyeProofOfConcept_1.0.5\packages' Install failed. Rolling back... Package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' does not exist in project 'ProofOfConceptWpf' Package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' already exists in folder 'D:\TFS\Prototyping\Main\Client\WebEyeProofOfConcept_1.0.5\packages' Added package 'WebEye.Controls.Wpf.StreamPlayerControl 1.0.6' to 'packages.config' Executing nuget actions took 3.01 sec Update-Package : Failed to add reference to 'WebEye.Controls.Wpf.StreamPlayerControl'. Error HRESULT E_FAIL has been returned from a call to a COM component. At line:1 char:1

  • Update-Package -reinstall
    • CategoryInfo : NotSpecified: (:) [Update-Package], Exception
    • FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.UpdatePackageCommand

Time Elapsed: 00:00:04.3360130

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jacobbo/WebEye/issues/69?email_source=notifications&email_token=AAN57QHJQW3WO6AL6QWINEDQZCLUXA5CNFSM4J3YLBN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IA7TMHQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN57QEL5RSCR64NNHFADNDQZCLUXANCNFSM4J3YLBNQ .

jacobbo commented 4 years ago

Can you try this project? https://drive.google.com/file/d/1LuZ5uIKYDfXNUM35STIbUlzxMFP8qhhp/view?usp=sharing

marekside commented 4 years ago

Hi,

I've fond the issue and I will explain it here. The fault was on my side, nevertheless the way how Visual studio behaved was very interesting. We are using two NuGet repositories. One is the official one, the second is an "in-house" for packages and dependencies built locally. One thing we have to do for process reasons is that we have to sign all the packages and dependencies we use in our project. The WebEye got signed as well and uploaded on the private repository. The problem was that the script for signing didn't work well so we didn't increased the version. So actually we had two WebEyes packages on two different repositories, one signed, one not. This caused the issue.

Thank you very much for your interest in solving the problem! I really appreciate your effort.

Regards, Marco.

On Tue, Dec 17, 2019 at 9:56 PM Alexander Iacobciuc < notifications@github.com> wrote:

Can you try this project?

https://drive.google.com/file/d/1LuZ5uIKYDfXNUM35STIbUlzxMFP8qhhp/view?usp=sharing

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jacobbo/WebEye/issues/69?email_source=notifications&email_token=AOB6EZTPYWEUQNEF47MZU73QZE4INA5CNFSM4J3YLBN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHD5S7Q#issuecomment-566745470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOB6EZXKRRO4LRVSFJF4D7TQZE4INANCNFSM4J3YLBNQ .

-- Regards, Marco Casamassima casamassima.marco@gmail.com