Profile_bird

Hey there! Wolfbyte is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving Wolfbyte's tweets.

Already using Twitter
from your phone? Click here.

Wolfbyte

  1. @OzSarge You alive over there buddy? How's everything going?
  2. Back from #MSFTVS2010 Roadshow Event. Was very interesting. Thoroughly enjoyed it.
  3. @andymlamb Have they got good coffee going on yet?
  4. @garry_stewart The one today. I didn't get into the original session (which is the one tomorrow).
  5. For those going to the VS2010 event in #perth at the Duxton, I'll be the guy who looks like a rabid koala and sounds like like he's dying :)
  6. Well bugger this. It takes me nearly an hour to get home so I'm starting. Byee
  7. @RhysC @graefoster Yeah that should be public Mike( IDrink drink ) { ... }
  8. @JakCharlton Yeah that's how I'd normally end up doing it. Was going to look into getting ObjectBuilder2 to do the Logging Facility trick
  9. @RhysC OK then , who has ILogger as a dependency if thats a cross cutting concern?
  10. @graefoster Fair enough but anything re-usable across projects eventually comes to rely on one container. Changing becomes hard
  11. @graefoster @RhysC I find myself using CSL precisely to avoid passing around the container. I guess thats purely psychological
  12. @RhysC Even for common infrastructure components such as Loggers?
  13. @graefoster The intent of CSL is just to allow other frameworks to rely on IoC Container without relying on a particular one.
  14. @JakCharlton http://perth.ozalt.net/ There is a google calendar there too which should make it easier to keep track of
  15. @JakCharlton Tomorrow Week (9th) Oh crap, I think I've been telling peeps the 16th...
  16. @graefoster Agreed. Especially when there's no way to know it's doing that from the outside of the component.
  17. @graefoster God objects are fine as long as you have a well-designated place for worship
  18. @JakCharlton OK fine but the point is there should be one point in the app that knows about the Container and the rest should be ignorant
  19. @RhysC Your team never need know what is in the "magic box"
  20. @RhysC also, hide your container behind CSL and then write an app specific wrapper for the container of your choice.