Relative Content

Tag Archive for asp.net-mvc

Provide multiple SendCompleted callbacks to SmtpClient

I have an Email class that has a Send method that optionally takes an SmtpClient and sends an email asynchronously using SendAsync. If no SmtpClient is supplied to this method, it instantiates a default SmtpClient and uses that to send the email. Inside the Send function, I provide a SendCompleted callback which disposes of the MailMessage and the default SmtpClient if one was not supplied to the method.

Provide multiple SendCompleted callbacks to SmtpClient

I have an Email class that has a Send method that optionally takes an SmtpClient and sends an email asynchronously using SendAsync. If no SmtpClient is supplied to this method, it instantiates a default SmtpClient and uses that to send the email. Inside the Send function, I provide a SendCompleted callback which disposes of the MailMessage and the default SmtpClient if one was not supplied to the method.

Provide multiple SendCompleted callbacks to SmtpClient

I have an Email class that has a Send method that optionally takes an SmtpClient and sends an email asynchronously using SendAsync. If no SmtpClient is supplied to this method, it instantiates a default SmtpClient and uses that to send the email. Inside the Send function, I provide a SendCompleted callback which disposes of the MailMessage and the default SmtpClient if one was not supplied to the method.

Provide multiple SendCompleted callbacks to SmtpClient

I have an Email class that has a Send method that optionally takes an SmtpClient and sends an email asynchronously using SendAsync. If no SmtpClient is supplied to this method, it instantiates a default SmtpClient and uses that to send the email. Inside the Send function, I provide a SendCompleted callback which disposes of the MailMessage and the default SmtpClient if one was not supplied to the method.

How to structure a modern web application

Background I recently developed, for two different projects, two web applications. The two followed quite different approaches. The first one was a classic inventory application (lists of stuff to view, select, edit.. very CRUD) and was developed with Razor and ASP.NET MVC: controller accepting requests, getting a model through a Repository, building different Viewmodels out […]

How to structure a modern web application

Background I recently developed, for two different projects, two web applications. The two followed quite different approaches. The first one was a classic inventory application (lists of stuff to view, select, edit.. very CRUD) and was developed with Razor and ASP.NET MVC: controller accepting requests, getting a model through a Repository, building different Viewmodels out […]

How to structure a modern web application

Background I recently developed, for two different projects, two web applications. The two followed quite different approaches. The first one was a classic inventory application (lists of stuff to view, select, edit.. very CRUD) and was developed with Razor and ASP.NET MVC: controller accepting requests, getting a model through a Repository, building different Viewmodels out […]

How to structure a modern web application

Background I recently developed, for two different projects, two web applications. The two followed quite different approaches. The first one was a classic inventory application (lists of stuff to view, select, edit.. very CRUD) and was developed with Razor and ASP.NET MVC: controller accepting requests, getting a model through a Repository, building different Viewmodels out […]