Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Irrespective of DD4T, you will need a workaround to inject dependencies in HttpModules (see this answeranswer for more), so I think your best bet is to do what you are doing - explicitly setting the resolver in your own implementation of the binary module- its unlikely that you want to change a publication resolver later anyway, and almost every project I worked on customized the default binary module/file manager in any case...

Irrespective of DD4T, you will need a workaround to inject dependencies in HttpModules (see this answer for more), so I think your best bet is to do what you are doing - explicitly setting the resolver in your own implementation of the binary module- its unlikely that you want to change a publication resolver later anyway, and almost every project I worked on customized the default binary module/file manager in any case...

Irrespective of DD4T, you will need a workaround to inject dependencies in HttpModules (see this answer for more), so I think your best bet is to do what you are doing - explicitly setting the resolver in your own implementation of the binary module- its unlikely that you want to change a publication resolver later anyway, and almost every project I worked on customized the default binary module/file manager in any case...

Source Link
Will Price
  • 16.4k
  • 1
  • 21
  • 61

Irrespective of DD4T, you will need a workaround to inject dependencies in HttpModules (see this answer for more), so I think your best bet is to do what you are doing - explicitly setting the resolver in your own implementation of the binary module- its unlikely that you want to change a publication resolver later anyway, and almost every project I worked on customized the default binary module/file manager in any case...