Hi List,

As a budding SharePoint developer, I was hoping there are some people on the
list here who can provide some guidance and/or anecdotes on selecting a
suitable IoC container for a custom SharePoint solution.

I started investigating this today and have become somewhat dismayed at how
inflexible it seems to be to deploy a container inside a SharePoint site.

Most containers I have looked at so far (Spring.NET, Autofac, Castle
Windsor) recommend modifying global.asax with a custom class that inherits
from SPHttpApplication.  Because our SharePoint Solution may be deployed
within arbritary SharePoint sites by the customer(s), am I correct in
assuming that this approach would make our product incompatible with a
customer's own potential global modifications?

An alternative I have read for Autofac is to insert Autofac's custom
HttpModules that control the container setup and tear down into the request
pipeline into the SharePoint site via web.config.  I have not fiddled with
the SharePoint web.config before but seem to recall reading blog posts that
discourage it because you either have to hack it during your solution
deployment, which won't work in 100% of deployment scenarios, or use
SPConfigModification, which has a gross API.

I'm at the point now where I am considering rolling my own extremely simple
container just so I don't have to deal with the deployment minefield.

Does anyone have some experiences to share which might help enlighten me? :)

Cheers,
Joe.
_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to