-
Notifications
You must be signed in to change notification settings - Fork 470
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
Constructor arguments vary by alphabetical order #230
Comments
sebastienros
added a commit
to sebastienros/Core
that referenced
this issue
Jan 28, 2017
sebastienros
added a commit
to sebastienros/Core
that referenced
this issue
Jan 28, 2017
Thanks @sebastienros for a detailed report and a pull request. I don't think this is related to #112 as that incomplete issue makes no mention of using mixins which this defect is in. |
Thanks @sebastienros for the pull request, I've made my review comments and merged to master, this will be released in v4.1. |
OMG sorry, I completely lost track on it. Thanks for fixing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a proxy from two instances, the constructor that will be called with the two instances and the
IInterceptor[]
parameters will have its arguments vary alphabetically on the implemented interfaces, and won't match the expected order hence throwing a "couldn't find parameterless constructor" error.Here is the repro:
This will throw an exception. Now if you rename
IFoo1
toIFoo3
which is alphabetically afterIFoo2
the constructor won't be found (the order of theconstructorArguments
and the actual ctor method don't match anymore)Environment: .NET Core 1.1 with Castle.Core 4.0.0
Maybe related to: #112
The text was updated successfully, but these errors were encountered: