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
Docs on implementing IOC unclear #342
Comments
Also, I've found that using Here's a stack trace from the backoffice:
|
Hi, @clausjensen has been working on getting these updated, sorry for the out-dated docs, we'll try to get this updated as soon as possible. Quite a lot of developers are using Autofac so would be worth searching or asking on the forum for advice: http://our.umbraco.org |
Thanks for the update. I'd love to help out, I feel quite strongly about dependency injection and IOC. I'll send a PR over and reference this issue when I get time to share what I've learned experimenting with DI in Umbraco. |
@glcheetham check your twitter ;) |
@clausjensen Thanks a bunch. So I can refer back to this issue in the future, your gist was just what I needed. I was struggling to figure out which of Umbraco's types I needed to register with Autofac to get the backoffice working again. |
Hi guys, Is it safe to assume this can be closed down? 😁 |
Yep I think we can close it for now .. can reopen if we think there's a need for further docs |
Brilliant! Thanks @clausjensen |
Think this needs opening again. https://docs.umbraco.com/umbraco-cms/reference/using-ioc might be ok for experts but it's not helping at wrt the registering of classes. Thought it was supposed to have been made easier?! The docs are very confusing and unclear. |
https://our.umbraco.org/documentation/reference/using-ioc
I found the documentation page on implementing IOC unclear, they don't specify that the given examples will not compile without a reference to the Autofac MVC package alongside the mentioned container Autofac. (For
ContainerBuilder.RegisterControllers
andAutofacDependencyResolver
)The text was updated successfully, but these errors were encountered: