StructureMap A Dependency Injection / Inversion of Control tool for .Net
Download

StructureMap Ranking & Summary

StructureMap Tags

physical dependency dependency code injection dependency analyzer .NET Dependency Injector Dependency Injector create dependency Injection Dependency Director Object Dependency color inversion Device dependency dependency injection container ObjectDefinitions Injection Unity Dependency Injection Library Injection test-driven development view dependency inversion dependency management Identify Dependency dependency lister list dependency search classpath dependency classpath dependency searcher dependency injection static dependency viewer view static dependency Phase Inversion Services Dependency Dependency Viewer Task Dependency dependency explorer Dependency Inversion Dependency Diagram Find Dependency Dependency Searcher Avoid Dependency Conflict Avoid Library Dependency File Dependency Database injection node dependency code dependency assembly dependency dependency finder search missing dependency Java dependency missing dependency dependency injection framework Dependency Browser Browse Dependency GUI Maps dependency Check Dependency dependency manager Java dependency management manage dependency dependency analysis external dependency dependency creator injection container Load Injection Framework load injection Dependency Structure Dependency Resolver Dependency Detector Inversion of Control dependency mapper analyze dependency dependency package include dependency

StructureMap Description

The StructureMap was designed to be a Dependency Injection / Inversion of Control tool for .Net that can be used to improve the architectural qualities of an object oriented system by reducing the mechanical costs of good design techniques. StructureMap can enable looser coupling between classes and their dependencies, improve the testability of a class structure, and provide generic flexibility mechanisms. Used judiciously, StructureMap can greatly enhance the opportunities for code reuse by minimizing direct coupling between classes and configuration mechanisms. Consider using StructureMap if you: - Require significant extensibility - Simply want a generic configuration tool - Want to support multiple deployment configurations - Are using a Test-Driven Development philosophy or want to largely automate testing - Want to isolate a troublesome subsystem or provide smooth migration paths away from legacy interfaces - Need a great deal of configurable properties or plugin hot spots Do not use StructureMap if an application or process requires little flexibility. The abstraction and indirection afforded by StructureMap is unnecessary and even harmful in simpler systems or processes.

StructureMap Related Software