1. Eng. Giorgetti Alessandro Software Artisan SID s.r.l.

2. Graduated Engineer Owner/co-founder of SID s.r.l. Blog: http://www.primordialcode.comhttp://www.primordialcode.com Email: guardian@nablasoft.comguardian@nablasoft.com Twitter: @A_Giorgetti

3. To be able to use an IoC/DI framework effectively you need to structure your application the right way! Your first problem is an Architectural problem: How to partition an application? How to structure each module? What are the interactions? Dependencies? …

4. Only When you’ve answered those questions, you can think of how to implement the solution! Only at this stage you can start thinking of which ‘tool’ to use and which ‘best practice’ you can follow to solve your problems!

5. When you think of an application architecture, usually this is the first thing it come into your mind: DAL Business Logic User Interface Securty Logging Infrastructure

6. When using a IoC/DI container your application sounds more like this: Security Service IService1 Module1 Logging Service IService2 Module2 Infrastructure Shell Application Framework IService3 Messaging Service

7. When implementing a module/service Module1 Module2 Infrastructure Shell Application Framework DAL Business Logic User Interface Securty Logging Infrastructure

8. Keep things simple! Use a top-down approach while defining and designing the application Break the application in modules / features and decouple the more you can: reusability, easy implementation Think using ‘interfaces’ (do not try to implement anything at this stage)…but avoid over- engineering

9. Design  Interfaces Component configuration, creation, lifecycle  IoC/DI/ServiceLocator, etc… Managing interactions  data storage, shared data, message brokering, etc…

10. You have plenty of ‘tools’ and ‘patterns’ that helps you implementing your solution: Layered applications Implementation patterns (MVC, MVVM, …) Reuse services

11. Eng. Giorgetti Alessandro

13. Inspired by this workshop I’ve started a series of articles on my blog you can check to dig into some of the arguments I proposed here: Silverlight, MVVM … and IoC http://www.primordialcode.com/blog/post/silverlight-mvvm-ioc-part-1 http://www.primordialcode.com/blog/post/silverlight-mvvm-ioc-part-2 Silverlight Navigation Framework … and IoC http://www.primordialcode.com/blog/post/silverlight-navigation-framework- resolve-pages-ioc-container More to come…

14. Eng. Giorgetti Alessandro