unity-container

I am new in the Wpf & Mvvm world , but I have found a couple of examples and just found that there is some different way to instantiate the model. I would like to know the best/correct way to do it. both ways are using Unity What I've foud: var navigatorView = new MainView(); navigatorView.DataContext = m_Container.Resolve<INavigatorViewModel>(); m_RegionManager.Regions["NavigatorRegion"].Add(navigatorView); What I did: var navigatorView = m_Container.Resolve<MainView>; m_RegionManager.Regions["NavigatorRegion"].Add(navigatorView); and I changed the constructor to receive viewmodel so I can

Hi I am trying to use Unity container in WPF MVVM application. I have not used Prism as it seems to heavy. Here is the application structure. I am trying to figure out how to resolve Views to ViewModels and dependencies of the view models (services). Application: Views MainWindow.xaml CustomerList.xaml CustomerDetail.xaml BookList.xaml BookDetail.xaml ViewModels MainViewModel CustomerListViewModel BoolListViewModel BookDetailViewModel CustomerDetailViewModel Library ICustomerService (AddCustomer, SaveCustomer, GetCustomers, GetCustomer) CustomerService:ICustomerService IBookService (GetBooks,

I've been working with Microsoft's Unity IOC container. There are a bunch of overloads for the RegisterType() method all looking similar to IUnityContainer RegisterType(Type t, params InjectionMember[] injectionMembers); I'm wondering when the injectionMembers parameters are for? I couldn't find any documentation for the them (even though they're in every overload) and none of the sample code I looked at use them. Am I missing something here? Are they not commonly used or did I just miss the examples? Jehof The overload with the InjectionMember array is used, when you do not provide a

I'd like to create an instance of a class using unity where the class has two constructors with the same number of parameters. Here is the instantiation: _unityContainer.Resolve<IGradeType>(new ParameterOverride("gradeTypeStringFromXmlFile", gradeTypeStringFromXmlFile)); And here are the constructors: public GradeType(string gradeTypeStringFromXmlFile) { _gradeTypeStringFromXmlFile = gradeTypeStringFromXmlFile; } public GradeType(Enum.GradeType gradeType) { _gradeType = gradeType; } If I try to do this I get an exception saying The type GradeType has multiple constructors of length 1. Unable

How do I registertype with the container where the type doesn't have NO PARAMETER constructor. In fact my constructor accepts a string, and I normally pass in a string that represents a Path. So when I do resolve it automatically creates the new type but passing in a string? It's simple. When you register the constructor, you just pass the value you want injected for the parameter. The container matches up your constructor based on the type of value (API) or name of parameter (XML). In the API, you'd do: container.RegisterType<MyType>(new InjectionConstructor("My string here")); That will

I have read often that Service Locators in IOC are an anti-pattern . Last year we introduced IOC (Ninject specifically) to our application at work. The app is legacy, it's very big and it's fragmented. There are lots of ways a class, or a chain of classes can get created. Some are created by the web framework (which is custom), some are created by nHibernate. Lots are just scattered around in weird places. How would we handle the different scenarios and not come up with something thats not at least ServiceLocatorish and not end up with different kernels in different places (scopes like

It could seem a stupid question because in my code everything is working, but I've registered a singleton this way with my Unity container _ambientContainer : _ambientContainer.RegisterType<Application.StateContext>(new ContainerControlledLifetimeManager()); In order to avoid to use my local field, I use: get { return ServiceLocator.Current.GetInstance<Application.StateContext>(); } inside my get property to get an instance of my object. This way I get always the same instance ( Application.StateContext is still a singleton) or does GetInstance create a new one? Is it better to use the local

Microsoft's Unity dependency injection framework can be configured either through code or through the applications configuration file (app.config). Code example: IUnityContainer container = new UnityContainer() .RegisterType<IInterface, ConcreteImplementation>(); Configuration example: <unity> <containers> <container> <types> <type type="IInterface, MyAssembly" mapTo="ConcreteImplementation, MyAssembly" /> What are the advantages/disadvantages to each approach? I can think of the obvious advantage "Users can easily configure your application", and the obvious disadvantage "Users can easily