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.

Sign up for GitHub

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

Jump to bottom

Bug: unregistered concrete type resolution fails for classes without parameterless constructors #114

Closed
TheTribe opened this issue Oct 3, 2013 · 0 comments
Closed

Bug: unregistered concrete type resolution fails for classes without parameterless constructors #114

TheTribe opened this issue Oct 3, 2013 · 0 comments
Assignees
@jbatte47
Milestone
3.10-beta.4

Comments

@TheTribe
Copy link
Contributor

TheTribe commented Oct 3, 2013

  • main point of vulnerability is concrete implementations of contracts in a DI context
  • unregistered contract instances should be mocks on activation
  • probably needs to be handled in MoqRegistrationSource -- will there be a way to replicate this capability in Ninject?
@ghost ghost assigned jbatte47 Oct 3, 2013
jbatte47 added a commit to jbatte47/code-patterns that referenced this issue Oct 4, 2013
@jbatte47
Issue patterns-group#114 - Fix for unregistered concrete type resolution
ea5a3b2 
- `Create<TService>` now proxies the underlying container resolver
- New method: `Create<TService, TImplementation>` for update-then-resolve usage
- Reproduced then verified fix in Autofac Moq Container feature
TheTribe pushed a commit that referenced this issue Oct 4, 2013
Merge pull request #115 from jbatte47/bugfix/issue-114
7e4258b 
Issue #114 - Fix for unregistered concrete type resolution
@TheTribe TheTribe closed this as completed Oct 4, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbatte47 jbatte47

Labels
None yet
Projects
None yet
Milestone
3.10-beta.4
Development

No branches or pull requests
1 participant
@jbatte47