Index
- about this release
- AdventureWorks Shopper
- annotating objects for constructor injection
- annotating objects for method call injection
- annotating objects for property (setter) injection
- API
- appendix
- applications
- architecture
- array values
- Aspect Oriented Programming (AOP)
- assemblies
- assembly matching rule
- attribute injection
- attribute-driven policies
- audience and system requirements
- authorization handler rule
- behaviors for interception
- benefits of Unity
- BuildUp methods
- call handlers
- case studies: customizing Unity
- case studies: using Unity in a Windows Store app
- changes in this release
- Chris Tavares
- circular references
- configuration
- constructor injection
- containers
- convention
- custom attribute matching rule
- custom interception behaviors
- decorator chains
- decorator pattern
- default and lifetime registrations
- default registrations
- deferring resolution of objects
- dependency injection
- dependency overrides
- deployment and operations
- derived types
- design concepts
- design goals
- design-time configuration
- developer's guide to dependency injection
- elements
- Enterprise Library call handlers
- Event Broker Extension QuickStart
- event broker extensions
- example code
- exception handling handler rule
- extensions
- factory patterns
- files
- fluent configuration interface
- foreword by Chris Tavares
- Func<T> type
- generic parameters and types
- generic types
- global assembly cache
- goals of this guide
- guidance
- handler precedence with attributes
- HandlerAttribute base class
- handlers
- hierarchies
- ICallHandler interface
- information
- injected parameter and property values
- injection
- InjectionMembers
- instances
- IntelliSense
- interception
- and dependency injection
- and policy injection
- behavior creation
- behavior pipeline
- behaviors for
- configuration files for
- configuration schema elements
- configuring containers for
- handler attributes creation
- in partial trust environments
- overview
- overview of techniques
- policy injection call handlers
- registering
- scenarios for
- stand-alone
- using in applications
- with containers
- with Unity
- InterceptionBehavior class
- Interceptor class
- interfaces
- introduction
- known issues
- Lazy<T>type
- legacy
- legacy interception configuration
- lifetime and default registrations
- lifetime management
- lifetime managers
- limitations
- links
- Liskov substitution principle
- logging handler rule
- logging handlers
- logging method invocation
- loose coupling
- managers
- mappings
- matching rules
- member name matching rule
- method call injection
- method signature matching rule
- methods
- migration
- Model View Presenter (MVP) pattern
- more information
- names
- namespace matching rule
- NotifyPropertyChangedBehavior class
- objects
- annotating for constructor injection
- annotating for method call injection
- annotating for property (setter) injection
- deferring the resolution of
- not created by the container
- resolving
- resolving by type
- resolving by types and registration names
- resolving of particular types
- resolving with overrides
- scope and lifetime
- operations
- overloads
- overrides
- overview
- parameter type matching rule
- parameters
- partial migration
- partial trust environments
- patterns & practices links
- performance counter handler
- pipelines
- pluggable architecture
- policies
- policy injection
- prerequisites
- private assemblies
- process flow
- properties
- property (setter) injection
- property matching rule
- proxies
- QuickStarts
- Registering Policy Injection Components
- RegisterInstance method
- RegisterType interception
- RegisterType method
- RegisterTypes method
- registration
- related patterns & practices links
- release
- requests
- requirements
- Resolve method
- ResolveAll method
- resolved objects
- return type matching rule
- roles
- rules
- assembly matching rule
- authorization handler
- custom attribute matching rule
- exception handling handler
- logging handler
- member name matching
- method signature matching rule
- namespace matching
- performance counter handler
- policy injection matching rules
- property matching rule
- return type matching rule
- tag attribute matching rule
- type matching rule
- parameter type matching
- run-time configuration
- scenarios
- schemas
- service locator pattern
- shared assemblies
- side-by-side execution and migration
- Silverlight
- stand-alone interception
- StopLight QuickStart
- StoplightPresenter class
- strong naming
- summary
- system requirements
- tag attribute matching rule
- TagAttributeMatchingRule class
- tales from the trenches: customizing Unity
- tales from the trenches: using Unity in a Windows Store app
- target audience and system requirements
- target method performance
- topics
- type matching rule
- types
- and generic parameters registration
- and type mapping registation
- default interceptors for
- in the configuration file
- interception of
- interception techniques
- interceptions
- interceptions using Unity
- registrations in the example
- resolving objects by
- resolving objects by registration names
- resolving objects of particular types
- stand-alone interception
- types of injection
- Unity
- 2.0 approach
- adding to applications
- adding to Web applications
- configuration
- constructing and disposing
- customization case study
- dependency injection and interception
- design goals of
- extending
- extending and modifying
- in applications
- in partial trust environments
- interception
- QuickStarts
- StopLight QuickStart
- this release
- when to use
- Windows Store app
- Windows Store app appendix
- UnityContainer
- UnityServiceLocator class
- validation handler
- values for injection
- versioning
- Visual Studio
- Visual Studio IntelliSense
- walkthroughs: Event Broker Extension QuickStart
- walkthroughs: Unity StopLight QuickStart
- Web applications
- welcome to Unity
- what does Unity do?
- what is Unity?
- when should I use Unity?
- who's who
- Windows Store apps
- xcopy command
- XSD