Next Release? When?

  • Thread starter Thread starter Scott Townsend
  • Start date Start date
S

Scott Townsend

I've been told that my SMTPClient issue will be fixed in a Future release.
How Often is the Framework updated? Is there a place to get Beta Versions so
I can test my app with the bug Fix?

Thank,
Scott<-
 
Scott,

Next version of .NET is not planned yet (at least no public info available).
I am sure Microsoft will make announcements, when beta versions become
available for download.

I've been told that my SMTPClient issue will be fixed in a Future release.
How Often is the Framework updated? Is there a place to get Beta Versions so
I can test my app with the bug Fix?

Thank,
Scott<-
 
So what about Patches and bugfixes? I'd hate to think they wont be fixing
the little bugs in the framework until the next big release??

There has to be something inbetween??

Thanks,
Scott<-
 
MS has stated that they plan for a mid-summer 2006 for SP1 for .Net 2.0 and
..Net 1.1.

Mike.
 
aaaarrrrggg... Hopefully they will provide me with a workaround for my bug
before then. )-; I don't think I can wait that long to convert over my
SQL2000 to SQL 20005 DTS jobs...

I suppose I could write a 1.1 .net app and import the function into the
2.0.net app

bugger!

Thanks!

Scott<-
 
When using a message object and the SMTPClinet - setting the
mailMessage.DeliveryNotificationOptions only works once per SMTP Connection.
so if you send out 3 emails only the first gets the RCPT TO:<email Address>
NOTIFY=SUCCESS in the SMTP protocol. All the rest are just send out as RCPT
TO:<email Address>, regardless of the setting of
mailMessage.DeliveryNotificationOptions



Here is the Bug feedback
http://lab.msdn.microsoft.com/Produ...edbackid=53d26f3b-e161-4993-93e5-f4d1e62d8754

Here is the MSDN Forum Post
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=154268&SiteID=1

Thanks,
Scott<-
 
First of all, not all mail domain return receipts and some only return
receipts on just successes or just failures.

Okay, a workaround you could consider is to use your list of recipients
within a foreach loop. For example:

Given a MailAddressCollection macTo and a MailAddress maFrom --

foreach (MailAddress maTo in macTo)
{
MailMessage msgMail = new MailMessage(maFrom, maTo)
msgMail.Subject = "<Subject Text Here>";
msgMail.Body = "<Body Text Here>";
msgMail.DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;

smtpMail = new SmtpServer("localhost");
smtpMail.Send(msgMail);
}

Hope this helps!
 
Thank you for your reply...

We understand that its just a delivery status and that they may only receive
a Success/Failure notification if anything at all. Our Sales people still
think the internet is FM and they just need a but more info to keep them in
check. (-;

I've confirmed this with MSS and they now have a Fix for it. They said its
in the Next Major Release, though I can call Support (on hold now) and get
it.

As for your code. If you take out your foreach loop and just do the:
smtpMail.Send(msgMail); twice or do:

smtpMail = new SmtpServer("localhost");
smtpMail2 = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail2.Send(msgMail);

or

MailMessage msgMail = new MailMessage(maFrom, maTo)
MailMessage msgMail2= new MailMessage(maFrom, maTo)
msgMail.Subject = "<Subject Text Here>";
msgMail2Subject = "<Subject Text Here>";
msgMail.Body = "<Body Text Here>";
msgMail2Body = "<Body Text Here>";
msgMail.DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
msgMail2DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
smtpMail = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail.Send(msgMail2;

or

MailMessage msgMail = new MailMessage(maFrom, maTo)
MailMessage msgMail2= new MailMessage(maFrom, maTo)
msgMail.Subject = "<Subject Text Here>";
msgMail2Subject = "<Subject Text Here>";
msgMail.Body = "<Body Text Here>";
msgMail2Body = "<Body Text Here>";
msgMail.DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
msgMail2DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;

smtpMail = new SmtpServer("localhost");
smtpMail2 = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail2.Send(msgMail);


You still just get the delivery receipt for the first connection to
"localhost"

Even though smtpMail goes out of scope, I set it to nothing, I force a
Garbage collection before and after the creation/send the connection to
"localhost" stays active after all of that. If I make any other attempts to
send amil after the initial connection no other delivery receipts are
generated. If after the first email is sent, and you wait several minute for
the SMTP connection to the server to drop, then you can send another message
and get the Delivery Status.

If you set the SmtpServer("<>") to different servers, you get one status per
server per connection.

I could send you my VB.Net app if you would like?

Thank you again for your reply...
Scott<-
 
Back
Top