惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
H
Help Net Security
量子位
The Cloudflare Blog
博客园 - Franky
博客园 - 聂微东
博客园 - 司徒正美
Last Week in AI
Last Week in AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
有赞技术团队
有赞技术团队
罗磊的独立博客
GbyAI
GbyAI
雷峰网
雷峰网
T
The Blog of Author Tim Ferriss
Martin Fowler
Martin Fowler
S
SegmentFault 最新的问题
美团技术团队
阮一峰的网络日志
阮一峰的网络日志
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
U
Unit 42
MongoDB | Blog
MongoDB | Blog

博客园 - 无名365

.NET 2.0 JSON Parser Provisioning 是什么意思? SOA与云计算 Good understand on WCF Data Contract & Serialization WCF DataContract EmitDefaultValue a xml configuration for unity and interception Programmatically Compress and Decompress Files using c# CodeRun Studio - A free cloud develop and debug service for .Net Cloud IDE 10个最“优秀”的代码注释 Compress and Decompress JQuery Mobile 1.0 Released, Gets Mixed Reaction Interceptor in Unity and Policy Injection in Unity Configuring Unity Container with Policy Injection Configuration Unity Configuration Node IoC and Unity - Configuration Objects and the Art of Data Modeling AppFabric Cache - Cache Cluster EF - How to delete an object without retrieving it LINQ to SQL Extension: Batch Deletion with Lambda Expression
Unity Configuration from Separate Configuration File
无名365 · 2011-11-22 · via 博客园 - 无名365

2011-11-22 09:42  无名365  阅读(757)  评论()    收藏  举报

I mentioned on Twitter the other day that if you have to configure Unity via a configuration file, you probably want to do it in a separate configuration file. Personally I think this is a best practice when using any of the Application Blocks in Enterprise Library, too, but I realize the experience can be a bit of a burden.

A few people asked me for an example of configuring Unity in a separate configuration file which is the motivation for this post. The Unity Documentation is pretty good on this topic. In fact, I pretty much just copy and pasted the code for reading from a separate file in this post, but this post might be a bit easier to find the information.

Reading Unity Configuration from Separate Configuration File

In this example, I am using a simple Console Application. The configuration information is in a separate configuration file, called unity.config, which has one container, called container, that maps a UserRepository to IUserRepository. The UserRepository constructor requires a connection string so I specified the connection string in the constructor parameters in the type configuration.

Program.cs

The GetContainer Method is pretty much boiler-plate code responsible for reading the unity.config file and populating a new container with the configuration information. You could make it more generic by passing in parameters for the name of the file, name of the container, etc. This is basically straight out of the documentation:

private static void Main(string[] args)

{

    IUnityContainer container = GetContainer();

    var repository = container.Resolve<IUserRepository>();

}

private static IUnityContainer GetContainer()

{

    var map = new ExeConfigurationFileMap();

    map.ExeConfigFilename = "unity.config";

    var config = ConfigurationManager.OpenMappedExeConfiguration(map, ConfigurationUserLevel.None);

    var section = (UnityConfigurationSection) config.GetSection("unity");

    var container = new UnityContainer();

    section.Containers["container"].Configure(container);

    return container;

}

Unity.config

The configuration file sets up some aliases, specifies the mapping between IUserRepository and UserRepository, provides an example of using a singleton lifetime manager, and contains type configuration that specifies how to construct the UserRepository:

<?xml version="1.0"?>

<configuration>

  <configSections>

    <section name="unity" type="Microsoft.Practices.Unity.Configuration.UnityConfigurationSection, Microsoft.Practices.Unity.Configuration" />

  </configSections>

  <unity>

    <typeAliases>

      <typeAlias alias="string" type="System.String, mscorlib" />

      <typeAlias alias="singleton" type="Microsoft.Practices.Unity.ContainerControlledLifetimeManager, Microsoft.Practices.Unity" />

      <typeAlias alias="IUserRepository" type="ConsoleApplication3.IUserRepository, ConsoleApplication3" />

      <typeAlias alias="UserRepository" type="ConsoleApplication3.UserRepository, ConsoleApplication3" />

    </typeAliases>

    <containers>

      <container name="container">

        <types>

          <type type="IUserRepository" mapTo="UserRepository" >

            <lifetime type="singleton" />

            <typeConfig extensionType="Microsoft.Practices.Unity.Configuration.TypeInjectionElement, Microsoft.Practices.Unity.Configuration">

              <constructor>

                <param name="connectionString" parameterType="string">

                  <value value="[YourConnectionString]"/>

                </param>

              </constructor>

            </typeConfig>

          </type>

        </types>

      </container>

    </containers>

  </unity>

</configuration>

IUserRepository and UserRepository

And last, a barebones illustration of the interface and concrete implementations of the types just to illustrate the use of the configuration file:

public interface IUserRepository {}

public class UserRepository : IUserRepository

{

    public string ConnectionString { get; private set; }

    public UserRepository(string connectionString) {

        ConnectionString = connectionString;

    }

}

Conclusion

Hopefully this helps you configure Unity in a separate configuration file. I think this is always a good idea as it keep your IoC / Dependency Injection configuration information separate from application settings in your app.config or web.config.

From http://www.pnpguidance.net/post/UnityConfigurationSeparateConfigurationFile.aspx