What I want from Sitecore for Christmas – Thoughts from an opinionated developer

Perhaps contentious perhaps not but as an API I’d like to see a little consistency in the dependencies in Sitecore. Specifically when you look at the various Sitecore modules shipped by them we have Ninject, Unity, SimpleInjector and so on. As hard as it might be to have a specific team move away from their chosen favourite library, for large scale installations we as customers need some consistency in the libraries we use and support in our installations.

I do accept that these modules are supposed to be ‘black box’ but they all end up in the same bin folder and so we as customers have to manage the dependencies. I’m currently working in a Unity shop and so have had to manage the installation of the ECM (which uses Unity 2.x) while we are using 3.5. That’s not so bad but we have these other containers floating around in there too.

So for Christmas I’d like to see a consistent choice in IOC. Or a standardised container interface I can use to inject my own container when using Sitecore modules from other vendors.

Advertisements

One thought on “What I want from Sitecore for Christmas – Thoughts from an opinionated developer

  1. Interesting point – it would be nice for Sitecore to pick standards and stick to them I guess, but I think no matter which IoC container they chose, it would always be frowned upon by some 😀

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s