What are the Pro's/Con's about using DotNetOpenMail vs. System.Web.Mail. I would like to transfer to DotNetOpenMail but I am having trouble convincing my boss it is worth it. Please give me a more solid argument. :)
Thanks,
Travis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If your boss is concerned with support, probably there are better alternatives than DotNetOpenMail. If I get hit by a truck or go berzerk, it would become unsupported unless some unlikely soul were to step in. And whenever I go on vacation (like the last couple weeks), or get really busy (the rest of the time), nothing happens. If support is a big issue, I'd go with aspNetEmail over System.Web.Mail; Dave Wanta is very good with turning around support requests. (I use aspNetEmail for one large project.)
As for the features differences between System.Web.Mail and the various open-source alternatives, it just depends on what your requirements are. The two limitations that made me give up on Microsoft's library are that a) it depends on CDONTS, which for me is messy, ugly and slow, and b) it is feature-poor and poorly designed. The features I needed were the ability to control the way the text version looks and to have full control over the way attachments work.
Ironically, DotNetOpenMail does a better job of leveraging the .net libraries than Microsoft's offering does. All System.Web.Mail does is act as an Adapter to pass your input off to some old Windows library. So there's no guarantee that the deployment environment will have these non-.net features set up (and functional). DotNetOpenMail, on the other hand, is 100% .Net.
Plus, if you have wacky requirements or just want to figure out how SMTP works, the DotNetOpenMail source is always here for you to play with.
Hope that helps,
-Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are the Pro's/Con's about using DotNetOpenMail vs. System.Web.Mail. I would like to transfer to DotNetOpenMail but I am having trouble convincing my boss it is worth it. Please give me a more solid argument. :)
Thanks,
Travis
Hi-
If your boss is concerned with support, probably there are better alternatives than DotNetOpenMail. If I get hit by a truck or go berzerk, it would become unsupported unless some unlikely soul were to step in. And whenever I go on vacation (like the last couple weeks), or get really busy (the rest of the time), nothing happens. If support is a big issue, I'd go with aspNetEmail over System.Web.Mail; Dave Wanta is very good with turning around support requests. (I use aspNetEmail for one large project.)
As for the features differences between System.Web.Mail and the various open-source alternatives, it just depends on what your requirements are. The two limitations that made me give up on Microsoft's library are that a) it depends on CDONTS, which for me is messy, ugly and slow, and b) it is feature-poor and poorly designed. The features I needed were the ability to control the way the text version looks and to have full control over the way attachments work.
Ironically, DotNetOpenMail does a better job of leveraging the .net libraries than Microsoft's offering does. All System.Web.Mail does is act as an Adapter to pass your input off to some old Windows library. So there's no guarantee that the deployment environment will have these non-.net features set up (and functional). DotNetOpenMail, on the other hand, is 100% .Net.
Plus, if you have wacky requirements or just want to figure out how SMTP works, the DotNetOpenMail source is always here for you to play with.
Hope that helps,
-Mike