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

"Could not load ControlzEx" #437

Closed
JVimes opened this issue May 17, 2017 · 5 comments
Closed

"Could not load ControlzEx" #437

JVimes opened this issue May 17, 2017 · 5 comments
Assignees
Labels

Comments

@JVimes
Copy link

JVimes commented May 17, 2017

If I add the Fluent.Ribbon NuGet package to a fresh WPF App, then following follow the basic setup instructions, I get a build warning:

Found conflicts between different versions of the same dependent assembly that could not be resolved.

And a runtime crash:

FileLoadException: Could not load file or assembly 'ControlzEx, Version=2.1.4.13, Culture=neutral, PublicKeyToken=f08b075e934b7045' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I was able to work around the problem by updating the ControlzEx package from the default, v2.1.1.3, to the latest allowed, v2.2.0.4.

More info

Detailed build output shows:

There was a conflict between "ControlzEx, Version=2.1.1.3, Culture=neutral, PublicKeyToken=f08b075e934b7045" and "ControlzEx, Version=2.1.4.13, Culture=neutral, PublicKeyToken=f08b075e934b7045".
    "ControlzEx, Version=2.1.1.3, Culture=neutral, PublicKeyToken=f08b075e934b7045" was chosen because it was primary and "ControlzEx, Version=2.1.4.13, Culture=neutral, PublicKeyToken=f08b075e934b7045" was not.
    References which depend on "ControlzEx, Version=2.1.1.3, Culture=neutral, PublicKeyToken=f08b075e934b7045" [C:\Users\username\Documents\Visual Studio 2017\Projects\WpfApp2\packages\ControlzEx.2.1.1.3\lib\net45\ControlzEx.dll].
        C:\Users\username\Documents\Visual Studio 2017\Projects\WpfApp2\packages\ControlzEx.2.1.1.3\lib\net45\ControlzEx.dll
          Project file item includes which caused reference "C:\Users\username\Documents\Visual Studio 2017\Projects\WpfApp2\packages\ControlzEx.2.1.1.3\lib\net45\ControlzEx.dll".
            ControlzEx, Version=2.1.1.3, Culture=neutral, PublicKeyToken=f08b075e934b7045, processorArchitecture=MSIL
    References which depend on "ControlzEx, Version=2.1.4.13, Culture=neutral, PublicKeyToken=f08b075e934b7045" [].
        C:\Users\username\Documents\Visual Studio 2017\Projects\WpfApp2\packages\Fluent.Ribbon.5.0.1.10\lib\net45\Fluent.dll
          Project file item includes which caused reference "C:\Users\username\Documents\Visual Studio 2017\Projects\WpfApp2\packages\Fluent.Ribbon.5.0.1.10\lib\net45\Fluent.dll".
            Fluent, Version=5.0.1.10, Culture=neutral, PublicKeyToken=3e436e32a8c5546f, processorArchitecture=MSIL

Here's the project:
WpfApp2.zip

And some other details on my environment:
image
image


Environment

  • Fluent.Ribbon v5.0.1.10
  • Windows 10
  • .NET Framework 4.6
    (Visual Studio 2017 Community)
@batzen
Copy link
Member

batzen commented May 17, 2017

I just tried the same guide and everything worked as expected.
Could you attach your project, as a zip archive, to this issue?

@JVimes
Copy link
Author

JVimes commented May 17, 2017

Sure, thanks! I just added the project and some more info.

@batzen
Copy link
Member

batzen commented May 17, 2017

Missed the part where you said that you fixed the problem by updating to the latest ControlzEx version.
Will have to update the nuget package to reference the version i compile Fluent.Ribbon with.
Always forget about these versions...

@batzen
Copy link
Member

batzen commented May 17, 2017

Will fix this beginning with version 6.0

@batzen batzen added this to the 6.0.0 milestone May 17, 2017
@batzen batzen self-assigned this May 17, 2017
@batzen batzen removed this from the 6.0.0 milestone Jun 5, 2017
@batzen
Copy link
Member

batzen commented Jun 5, 2017

Fixed in v5.0.2

@batzen batzen closed this as completed Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants