I'm using to create good emails.
However one thing that is uncertain to me is that I have 2 projects currently in order to organize code one for MVC and one for my repo and service layer.
My second project has no knowledge of MVC and I would like to keep it like this.
I am thinking that my SMTP code goes into a service layer or cover and then I tell it from other service layers when I need to send an email.
So where does the MVC fit into the mailer? Do I produce the body in the controller, then pass it to the Serivas layer near my SMTP class? "post-text" itemprop = "text">
MVC mailer already has support for sending emails. If you set up the conference correctly, then it should be able to email to Melvaris, without any additional implementation population.
I do not have the role of your second project in your solution, but these are two possibilities:
-
Maybe not practical ... "sending an email from the background "Wait for the version with"
-
Forget your SMTP from your other project and make a visual call using the HTTP which in turn will call MVCMailer < / Li>
Comments
Post a Comment