ASP.NET MVC 2 自动映射器放置

发布于 2024-09-25 23:08:48 字数 234 浏览 6 评论 0原文

我正在使用 Automapper 在 EF4 模型和 ViewModel 之间进行转换。 Automapper 需要声明映射关系，我发现自己将它们复制/粘贴到每个控制器的构造函数中。

Mapper.CreateMap<CoolObject, CoolObjectViewModel>();

我可以在哪里放置映射声明，以便它们只被调用一次，而不是每次实例化控制器时？这可能吗？

原文

I am using Automapper to convert between my EF4 Models and my ViewModels. Automapper needs map relationships declared and I find myself copy/pasting them inside every controller's constructor.

Mapper.CreateMap<CoolObject, CoolObjectViewModel>();

Where can I place the mapping declarations so they will only be called once and not every time a controller is instantiated? Is this possible?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

故人如初 2024-10-02 23:08:48

您可以将其放在 global.asax 的 application_start() 中。

目前，我有一个从 application_start 调用的静态方法，该方法初始化所有映射。 Library.AutoMapping.RegisterMaps();

AutoMapper.Mapper.CreateMap(typeof(CoolObject), typeof(CoolObjectViewModel));

AutoMapper.Mapper.CreateMap<CoolObject, CoolObjectViewModel>()
    .ForMember(d => d.Property1, f => f.MapFrom(s => s.Property1))
    .ForMember(d => d.Property2, f => f.MapFrom(s => s.Property2))
    .ForMember(d => d.Property3, f => f.MapFrom(s => s.Property3));

所以我的控制器看起来像这样。您会注意到 HomeController 构造函数需要 IDataContext。我在 RequestScope 级别上向 Ninject 注册 IDataContext，并为我实例化 DataContext 并将其注入到我的控制器中。这就是我的请求级别存储库的来源。

public class HomeController : Controller {

    IDataContext dataContext;

    public HomeController(IDataContext dataContext) {
        this.dataContext = dataContext;
    }
}

我在这里有关于 Ninject 的稍微更详细的解释 http://buildstarted.com/2010/08/24/dependency-injection-with-ninject-moq-and-unit-testing/

You can put it in the application_start() of the global.asax

Currently I have a static method that I call from the application_start that initializes all my mappings. Library.AutoMapping.RegisterMaps();

AutoMapper.Mapper.CreateMap(typeof(CoolObject), typeof(CoolObjectViewModel));

AutoMapper.Mapper.CreateMap<CoolObject, CoolObjectViewModel>()
    .ForMember(d => d.Property1, f => f.MapFrom(s => s.Property1))
    .ForMember(d => d.Property2, f => f.MapFrom(s => s.Property2))
    .ForMember(d => d.Property3, f => f.MapFrom(s => s.Property3));

So my Controller looks something like this. You'll notice that the HomeController constructor requires an IDataContext. I register IDataContext with Ninject on a RequestScope level and a DataContext is instantiated for me and injected into my controller. This is where my request level repository comes from.

public class HomeController : Controller {

    IDataContext dataContext;

    public HomeController(IDataContext dataContext) {
        this.dataContext = dataContext;
    }
}

I have a slightly more detailed explanation about Ninject here http://buildstarted.com/2010/08/24/dependency-injection-with-ninject-moq-and-unit-testing/

回复收藏 0 原文

~没有更多了~