Closed GoogleCodeExporter closed 8 years ago
Thanks for the suggestion. RegisterTypes() is the way to go. I'd held off on
this because the extra surface area doesn't seem justified when compared with
the small amount of code required to do this by hand. Looking at it now though
it does make an improvement to the consistency of registration code so we
should include it.
Original comment by nicholas...@gmail.com
on 9 Mar 2011 at 9:40
What about Removing RegisterAssemblyTypes and make an RegisterTypes overload
which receives an params array of assemblies?
Original comment by lanwin...@gmail.com
on 9 Mar 2011 at 9:47
Nicholas, I guess, lanwin wants more functionality from RegisterTypes method,
than simply doing RegisterType for each type in the list. He wants to get
IRegistrationBuilder<object, ScanningActivatorData, DynamicRegistrationStyle>
as a result from this method to customize all these types as one registration.
And it seems not so easy to implement by hand looking on how
RegisterAssemblyTypes is implemented: it would require all of the code from
ScanningRegistrationExtensions except for the line "assemblies.SelectMany(a =>
a.GetTypes()", which is replaced with simply "types".
Original comment by mrdont@mail.ru
on 23 Mar 2011 at 6:42
Maybe that could be better solved via #332
Original comment by lanwin...@gmail.com
on 23 Jun 2011 at 9:15
Original comment by travis.illig
on 21 Sep 2012 at 4:31
Original comment by travis.illig
on 5 Dec 2012 at 6:31
I think a RegisterTypes option that takes a list of types rather than a list of
assemblies would be pretty easy to provide and wouldn't conflict with
RegisterAssemblyTypes. I'll add it.
Original comment by travis.illig
on 5 Dec 2012 at 6:34
This issue was closed by revision dbc6235acdf6.
Original comment by travis.illig
on 5 Dec 2012 at 6:49
Original issue reported on code.google.com by
lanwin...@gmail.com
on 3 Mar 2011 at 1:38