Autofac Parent class and child class implementing same Interface











up vote
0
down vote

favorite












I want to resolve a parent class which takes a child class as a parameter and both implements the same interface.



How should I go about writing the AutoFac bootstrap file to resolve the EmailNotifier?



When I try to resolve I get the circular dependency error. Following is the code. I Already tried builder.RegisterAssemblyTypes this brings only the child implementation



   using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Autofac;

namespace AutoFactTest
{
// This interface lets you send some content
// to a specified destination.
public interface ISender
{
string Send(string message);
}

// We can implement the interface for different
// "sending strategies":
public class PostalServiceSender : ISender
{
public string Send(string message)
{
return message;
}
}
public class EmailNotifier : ISender
{
ISender _postal;

public EmailNotifier(ISender postal)
{
_postal = postal;
}
public string Send(string message)
{
return "EMail " + message;
}

public string DoSomethingElse(string message)
{
return "Do Something Else with " + Send(message);
}
}

public class PostalModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterType<PostalServiceSender>().AsSelf().As<ISender>().InstancePerDependency();
}
}

public class EmailModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterModule<PostalModule>();
builder.RegisterType<EmailNotifier>().AsSelf().As<ISender>().InstancePerDependency();
}
}


class Program
{
static void Main(string args)
{
var builder = new ContainerBuilder();
builder.RegisterModule<EmailModule>();
//This doesn't work because it takes only child implementation
// builder.RegisterAssemblyTypes(typeof(EmailNotifier).Assembly)
//.Where(x => x.Name.EndsWith("Sender"))
//.AsImplementedInterfaces();
var container = builder.Build();

ISender sender = container.Resolve<ISender>();
var output = container.Resolve<EmailNotifier>(new Autofac.NamedParameter("postal", sender));
}
}
}









share|improve this question






















  • This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
    – Travis Illig
    Nov 19 at 19:44















up vote
0
down vote

favorite












I want to resolve a parent class which takes a child class as a parameter and both implements the same interface.



How should I go about writing the AutoFac bootstrap file to resolve the EmailNotifier?



When I try to resolve I get the circular dependency error. Following is the code. I Already tried builder.RegisterAssemblyTypes this brings only the child implementation



   using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Autofac;

namespace AutoFactTest
{
// This interface lets you send some content
// to a specified destination.
public interface ISender
{
string Send(string message);
}

// We can implement the interface for different
// "sending strategies":
public class PostalServiceSender : ISender
{
public string Send(string message)
{
return message;
}
}
public class EmailNotifier : ISender
{
ISender _postal;

public EmailNotifier(ISender postal)
{
_postal = postal;
}
public string Send(string message)
{
return "EMail " + message;
}

public string DoSomethingElse(string message)
{
return "Do Something Else with " + Send(message);
}
}

public class PostalModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterType<PostalServiceSender>().AsSelf().As<ISender>().InstancePerDependency();
}
}

public class EmailModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterModule<PostalModule>();
builder.RegisterType<EmailNotifier>().AsSelf().As<ISender>().InstancePerDependency();
}
}


class Program
{
static void Main(string args)
{
var builder = new ContainerBuilder();
builder.RegisterModule<EmailModule>();
//This doesn't work because it takes only child implementation
// builder.RegisterAssemblyTypes(typeof(EmailNotifier).Assembly)
//.Where(x => x.Name.EndsWith("Sender"))
//.AsImplementedInterfaces();
var container = builder.Build();

ISender sender = container.Resolve<ISender>();
var output = container.Resolve<EmailNotifier>(new Autofac.NamedParameter("postal", sender));
}
}
}









share|improve this question






















  • This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
    – Travis Illig
    Nov 19 at 19:44













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I want to resolve a parent class which takes a child class as a parameter and both implements the same interface.



How should I go about writing the AutoFac bootstrap file to resolve the EmailNotifier?



When I try to resolve I get the circular dependency error. Following is the code. I Already tried builder.RegisterAssemblyTypes this brings only the child implementation



   using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Autofac;

namespace AutoFactTest
{
// This interface lets you send some content
// to a specified destination.
public interface ISender
{
string Send(string message);
}

// We can implement the interface for different
// "sending strategies":
public class PostalServiceSender : ISender
{
public string Send(string message)
{
return message;
}
}
public class EmailNotifier : ISender
{
ISender _postal;

public EmailNotifier(ISender postal)
{
_postal = postal;
}
public string Send(string message)
{
return "EMail " + message;
}

public string DoSomethingElse(string message)
{
return "Do Something Else with " + Send(message);
}
}

public class PostalModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterType<PostalServiceSender>().AsSelf().As<ISender>().InstancePerDependency();
}
}

public class EmailModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterModule<PostalModule>();
builder.RegisterType<EmailNotifier>().AsSelf().As<ISender>().InstancePerDependency();
}
}


class Program
{
static void Main(string args)
{
var builder = new ContainerBuilder();
builder.RegisterModule<EmailModule>();
//This doesn't work because it takes only child implementation
// builder.RegisterAssemblyTypes(typeof(EmailNotifier).Assembly)
//.Where(x => x.Name.EndsWith("Sender"))
//.AsImplementedInterfaces();
var container = builder.Build();

ISender sender = container.Resolve<ISender>();
var output = container.Resolve<EmailNotifier>(new Autofac.NamedParameter("postal", sender));
}
}
}









share|improve this question













I want to resolve a parent class which takes a child class as a parameter and both implements the same interface.



How should I go about writing the AutoFac bootstrap file to resolve the EmailNotifier?



When I try to resolve I get the circular dependency error. Following is the code. I Already tried builder.RegisterAssemblyTypes this brings only the child implementation



   using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Autofac;

namespace AutoFactTest
{
// This interface lets you send some content
// to a specified destination.
public interface ISender
{
string Send(string message);
}

// We can implement the interface for different
// "sending strategies":
public class PostalServiceSender : ISender
{
public string Send(string message)
{
return message;
}
}
public class EmailNotifier : ISender
{
ISender _postal;

public EmailNotifier(ISender postal)
{
_postal = postal;
}
public string Send(string message)
{
return "EMail " + message;
}

public string DoSomethingElse(string message)
{
return "Do Something Else with " + Send(message);
}
}

public class PostalModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterType<PostalServiceSender>().AsSelf().As<ISender>().InstancePerDependency();
}
}

public class EmailModule : Module
{
protected override void Load(ContainerBuilder builder)
{
builder.RegisterModule<PostalModule>();
builder.RegisterType<EmailNotifier>().AsSelf().As<ISender>().InstancePerDependency();
}
}


class Program
{
static void Main(string args)
{
var builder = new ContainerBuilder();
builder.RegisterModule<EmailModule>();
//This doesn't work because it takes only child implementation
// builder.RegisterAssemblyTypes(typeof(EmailNotifier).Assembly)
//.Where(x => x.Name.EndsWith("Sender"))
//.AsImplementedInterfaces();
var container = builder.Build();

ISender sender = container.Resolve<ISender>();
var output = container.Resolve<EmailNotifier>(new Autofac.NamedParameter("postal", sender));
}
}
}






autofac autofac-module






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 at 12:40









AllSpark

1561213




1561213












  • This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
    – Travis Illig
    Nov 19 at 19:44


















  • This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
    – Travis Illig
    Nov 19 at 19:44
















This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
– Travis Illig
Nov 19 at 19:44




This looks straight out of the FAQ which has concrete suggestions... Like not having the same interface mean two different things. What have you tried so far? Please update the question with this info rather than respond here in comments.
– Travis Illig
Nov 19 at 19:44

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374868%2fautofac-parent-class-and-child-class-implementing-same-interface%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374868%2fautofac-parent-class-and-child-class-implementing-same-interface%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy