I think also some burden should be placed on the audience as well. I would’ve preferred a requirement that the audience should be comfortable w. some cab concepts before attending the session. Or, just offer a beginners CAB presentation for such ppl. I am more interested in intermediate to advanced cab work. There was at least one individual that obviously had a poor understanding of CAB and kept interrupting the flow.

I think some of the stuff that was mentioned in the presentation actually started going in the intermediate/advanced direction. For instance, the discussion about MVC (especially supervising presenter) and so forth. Another foray was when you mentioned that OB (in your opinion) was a DI ‘framework framework’. That would have made a great subtopic. For instance, do you mean that we can replace OB w. Spring.NET, or our own framework? How about some guidelines and best practice recommendations.

Also I would’ve loved to hear about your implementation of ‘State’ replacement. How about replacing ‘State’ w. EntLib Caching block and so forth.

Anyways, thank for the talk and hope we get a lot more in future.

Anyone who thought they were going to walk out of any short presentation with a strong understanding of CAB clearly never attempted to wrap their head around it. It is huge, but it is hugely powerful and elegant when you understand how to leverage it.

Thanks for tackling such a relevant/complex subject in your presentation. You did an excellent job.

Looking forward to my first code camp if this topic is covered there.

As I mentioned last night, there is so much material in CAB that it needs a solid month of training, and a single UG presentation is definitely a tease and shortchanges the topic. Although it was good to see what’s involved, I’m afraid it may have overwhelmed some people a bit. As soon as we started to grasp one feature, you were on to the next (through no fault of your own — it is a lot to fit in).

I would prefer having multiple presentations, focusing on a topic at a time, from the guidance software on down. But I understand that is probably not best for UGs — it’s more of a training topic than in introduction and overview.

My recommendation for tweaking subsequent presentations is to spend a lot of time giving a high-level overview of the architecture without digging into code, and leave some specific code portions for Code Camps, training courses, or even your blog.

I know UG attendees love seeing code, this topic may require too much of a learning curve to dive into code so early.

I’d love to see the presentation again at another UG as it evolves.

I misspelled the word dependency (I usually turn spell check off in office - bad habit, i know!) Anyway, ObjectBuilder and DI are some of the things I’d like to dig into at the NJ CodeCamp if Scott & Don give me the say-so.

Hope to see you there…