I have this class :
public class Repo
{
public Repo() : this(ConfigurationManager.AppSettings[\"identity\"], ConfigurationManager.AppSettings[\"pass
Just try to register type this way:
<register type="IRepo" mapTo="Repo">
<constructor />
</register>
Because of no param
element specified in constructor
element it should call default constructor.
You can also do this registration in code:
container.RegisterType<IRepo, Repo>(new InjectionConstructor());
Unity by default picks the constructor with the most parameters. You have to tell Unity to use a different one explicitly.
One way to do this is with the [InjectionConstructor] attribute like this:
using Microsoft.Practices.Unity;
public class Repo
{
[InjectionConstructor]
public Repo() : this(ConfigurationManager.AppSettings["identity"], ConfigurationManager.AppSettings["password"])
{
}
public Repo(string identity,string password)
{
//Initialize properties.
}
}
A second way of doing this, if your opposed to cluttering up classes/methods with attributes, is to specify which constructor to use when configuring your container using an InjectionConstructor:
IUnityContainer container = new UnityContainer();
container.RegisterType<Repo>(new InjectionConstructor());
From the documentation:
How Unity Resolves Target Constructors and Parameters
When a target class contains more than one constructor, Unity will use the one that has the InjectionConstructor attribute applied. If there is more than one constructor, and none carries the InjectionConstructor attribute, Unity will use the constructor with the most parameters. If there is more than one such constructor (more than one of the "longest" with the same number of parameters), Unity will raise an exception.
I had a more simple problem that resulted in this error.
The container that I was using was the wrong container. I had accidentally created two different containers and my container.RegisterType<Interface,ConcreteObject> was inside of another container from the one being used.