Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank
10  1000 
Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation had
fundamental flaws. For example, attachment could only be added from files,
not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and
has a richer featureset.
Best regards,
Henning Krause
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.googlegro ups.com...
Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank
On Mar 27, 3:59 pm, "Henning Krause [MVP - Exchange]"
<newsgroups_rem...@this.infinitec.dewrote:
Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation had
fundamental flaws. For example, attachment could only be added from files,
not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and
has a richer featureset.
Best regards,
Henning Krause
"Frank" <frk....@gmail.comwrote in message
news:11*********************@n59g2000hsh.googlegro ups.com...
Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank- Hide quoted text -
- Show quoted text -
Hi Mr. Krause,
many thxs http://www.systemwebmail.com/ http://www.systemnetmail.com/
On Mar 27, 3:59 pm, "Henning Krause [MVP - Exchange]"
<newsgroups_rem...@this.infinitec.dewrote:
>Hello,
in .NET 1.1, only the System.Web.Mail was available. This
implemenation had fundamental flaws. For example, attachment could
only be added from files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more
flexible and has a richer featureset.
Best regards,
Henning Krause
"Frank" <frk....@gmail.comwrote in message
news:11*********************@n59g2000hsh.googlegr oups.com...
>>Hi,
I am hoping to find out the differences between the System.Net.Mail
and System.Web.Mail.
Can some nice folks post the differences; or some urls which show
the differences?
Great Thanks
Frank- Hide quoted text -
- Show quoted text -
Hi Mr. Krause,
many thxs
On Mar 27, 8:33 pm, Jay Parzych <jimp...@cox.netwrote:
http://www.systemwebmail.com/
http://www.systemnetmail.com/
On Mar 27, 3:59 pm, "Henning Krause [MVP - Exchange]"
<newsgroups_rem...@this.infinitec.dewrote:
Hello,
in .NET 1.1, only the System.Web.Mail was available. This
implemenation had fundamental flaws. For example, attachment could
only be added from files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more
flexible and has a richer featureset.
Best regards,
Henning Krause
"Frank" <frk....@gmail.comwrote in message
>news:11*********************@n59g2000hsh.googlegr oups.com...
>Hi,
>I am hoping to find out the differences between the System.Net.Mail
and System.Web.Mail.
>Can some nice folks post the differences; or some urls which show
the differences?
>Great Thanks
Frank- Hide quoted text -
- Show quoted text -
Hi Mr. Krause,
many thxs- Hide quoted text -
- Show quoted text -
great thxs!
Actually System.Net.Mail replaces System.Web.Mail, which is now marked
as obsolete.
Henning Krause [MVP - Exchange] wrote:
Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation
had fundamental flaws. For example, attachment could only be added from
files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible
and has a richer featureset.
Best regards,
Henning Krause
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.googlegro ups.com...
>Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank
--
Göran Andersson
_____ http://www.guffa.com
re:
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete
It's only "obsolete" for the .Net Framework 2.0.
It's still supported in the .Net Framework 1.0 and 1.1.
The correct term when a class works in previous
versions, but not in a later one, is "deprecated".
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message news:%2****************@TK2MSFTNGP02.phx.gbl...
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete.
Henning Krause [MVP - Exchange] wrote:
>Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation had fundamental flaws.
For example, attachment could only be added from files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and has a richer
featureset.
Best regards,
Henning Krause
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.googlegr oups.com...
>>Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank
--
Göran Andersson
_____
http://www.guffa.com
Juan T. Llibre wrote:
re:
>Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete
It's only "obsolete" for the .Net Framework 2.0.
It's still supported in the .Net Framework 1.0 and 1.1.
Obviously, as System.Net.Mail doesn't exist in framework 1.x.
The correct term when a class works in previous
versions, but not in a later one, is "deprecated".
The class is marked as obsolete using the Obsolete attribute. The
correct term for a class marked as obsolete is obsolete. You can also
call it "deprecated" as some other systems use that term for the same thing.
An obsolete class is still working, it's only recommended that it's not
used. As the framework is supposed to be able to run code compiled for
previos versions, classes can't just stop working, at least not until
they have been obsolete for some version updates.
>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message news:%2****************@TK2MSFTNGP02.phx.gbl...
>Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete.
Henning Krause [MVP - Exchange] wrote:
>>Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation had fundamental flaws.
For example, attachment could only be added from files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and has a richer
featureset.
Best regards,
Henning Krause
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.googleg roups.com...
Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks
Frank
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____ http://www.guffa.com
re:
The class is marked as obsolete using the Obsolete attribute.
There's conflicting info on that.
See : http://msdn2.microsoft.com/en-us/lib...il(VS.80).aspx
That page says that the classes in the System.Web.Mail namespace have been deprecated,
but all its classes have been marked as obsolete.
The namespace is not obsolete. It's deprecated.
That's because it doesn't work in the current version but works in the previous ones.
See: http://en.wikipedia.org/wiki/Deprecated
"The deprecated feature still works in the current version of the software,
but it may raise error messages or warnings recommending an alternative practice."
and http://www.w3.org/TR/WD-html40-970917/convent.html
"A deprecated element or attribute is one that has been outdated by newer constructs."
System.Web.Mail can be thought of as "obsolescent", but not "obsolete", since it still works.
Ymmv, of course.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message news:eU**************@TK2MSFTNGP06.phx.gbl...
Juan T. Llibre wrote:
>re:
>>Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete
It's only "obsolete" for the .Net Framework 2.0.
It's still supported in the .Net Framework 1.0 and 1.1.
Obviously, as System.Net.Mail doesn't exist in framework 1.x.
>The correct term when a class works in previous
versions, but not in a later one, is "deprecated".
The class is marked as obsolete using the Obsolete attribute. The correct term for a class marked
as obsolete is obsolete. You can also call it "deprecated" as some other systems use that term for
the same thing.
An obsolete class is still working, it's only recommended that it's not used. As the framework is
supposed to be able to run code compiled for previos versions, classes can't just stop working, at
least not until they have been obsolete for some version updates.
>>
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>>Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete.
Henning Krause [MVP - Exchange] wrote:
Hello,
in .NET 1.1, only the System.Web.Mail was available. This implemenation had fundamental flaws.
For example, attachment could only be added from files, not from Streams.
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and has a richer
featureset.
Best regards,
Henning Krause
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.google groups.com...
Hi,
>
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
>
Can some nice folks post the differences; or some urls which show the
differences?
>
Great Thanks
Frank
>
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____
http://www.guffa.com
Juan T. Llibre wrote:
re:
>The class is marked as obsolete using the Obsolete attribute.
There's conflicting info on that.
Not at all. It's very simple. There is an Obsolete attribute. There is
no Deprecated attribute. You can mark a class as obsolete, but you can't
mark it as deprecated.
See :
http://msdn2.microsoft.com/en-us/lib...il(VS.80).aspx
That page says that the classes in the System.Web.Mail namespace have been deprecated,
but all its classes have been marked as obsolete.
The namespace is not obsolete. It's deprecated.
That's because it doesn't work in the current version but works in the previous ones.
That is not correct. The classes still work in the current version.
See:
http://en.wikipedia.org/wiki/Deprecated
"The deprecated feature still works in the current version of the software,
but it may raise error messages or warnings recommending an alternative practice."
and
http://www.w3.org/TR/WD-html40-970917/convent.html
"A deprecated element or attribute is one that has been outdated by newer constructs."
System.Web.Mail can be thought of as "obsolescent", but not "obsolete", since it still works.
I think that you are confusing this with something else. Just because
something is obsolete doesn't in any way imply that it would not work
any more.
Ymmv, of course.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message news:eU**************@TK2MSFTNGP06.phx.gbl...
>Juan T. Llibre wrote:
>>re:
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete
It's only "obsolete" for the .Net Framework 2.0.
It's still supported in the .Net Framework 1.0 and 1.1.
Obviously, as System.Net.Mail doesn't exist in framework 1.x.
>>The correct term when a class works in previous
versions, but not in a later one, is "deprecated".
The class is marked as obsolete using the Obsolete attribute. The correct term for a class marked
as obsolete is obsolete. You can also call it "deprecated" as some other systems use that term for
the same thing.
An obsolete class is still working, it's only recommended that it's not used. As the framework is
supposed to be able to run code compiled for previos versions, classes can't just stop working, at
least not until they have been obsolete for some version updates.
>>Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl.. .
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete.
Henning Krause [MVP - Exchange] wrote:
Hello,
>
in .NET 1.1, only the System.Web.Mail was available. This implemenation had fundamental flaws.
For example, attachment could only be added from files, not from Streams.
>
The .NET 2.0 implementation is System.Net.Mail and is much more flexible and has a richer
featureset.
>
Best regards,
Henning Krause
>
>
"Frank" <fr*****@gmail.comwrote in message
news:11*********************@n59g2000hsh.googl egroups.com...
>Hi,
>>
>I am hoping to find out the differences between the
>System.Net.Mail and System.Web.Mail.
>>
>Can some nice folks post the differences; or some urls which show the
>differences?
>>
>Great Thanks
>Frank
>>
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____ http://www.guffa.com
I think we mostly have a semantic difference.
In practice, "obsolete" and "deprecated" are semantic synonyms.
re:
The classes still work in the current version.
You're right about that.
re:
>System.Web.Mail can be thought of as "obsolescent", but not "obsolete", since it still works.
I think that you are confusing this with something else.
I don't think so.
"obsolete" and "deprecated", in the sense they are used in CS,
means that they still work...but are on the way to not working.
At some point in the near ( maybe not so near ) future,
they will cease to work in the newest version.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message news:Ob**************@TK2MSFTNGP06.phx.gbl...
Juan T. Llibre wrote:
>re:
>>The class is marked as obsolete using the Obsolete attribute.
There's conflicting info on that.
Not at all. It's very simple. There is an Obsolete attribute. There is no Deprecated attribute.
You can mark a class as obsolete, but you can't mark it as deprecated.
>See :
http://msdn2.microsoft.com/en-us/lib...il(VS.80).aspx
That page says that the classes in the System.Web.Mail namespace have been deprecated,
but all its classes have been marked as obsolete.
The namespace is not obsolete. It's deprecated.
That's because it doesn't work in the current version but works in the previous ones.
That is not correct. The classes still work in the current version.
>See:
http://en.wikipedia.org/wiki/Deprecated
"The deprecated feature still works in the current version of the software,
but it may raise error messages or warnings recommending an alternative practice."
and
http://www.w3.org/TR/WD-html40-970917/convent.html
"A deprecated element or attribute is one that has been outdated by newer constructs."
System.Web.Mail can be thought of as "obsolescent", but not "obsolete", since it still works.
I think that you are confusing this with something else. Just because something is obsolete
doesn't in any way imply that it would not work any more.
>Ymmv, of course.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message
news:eU**************@TK2MSFTNGP06.phx.gbl...
>>Juan T. Llibre wrote:
re:
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete
It's only "obsolete" for the .Net Framework 2.0.
It's still supported in the .Net Framework 1.0 and 1.1.
Obviously, as System.Net.Mail doesn't exist in framework 1.x.
The correct term when a class works in previous
versions, but not in a later one, is "deprecated".
The class is marked as obsolete using the Obsolete attribute. The correct term for a class
marked as obsolete is obsolete. You can also call it "deprecated" as some other systems use that
term for the same thing.
An obsolete class is still working, it's only recommended that it's not used. As the framework
is supposed to be able to run code compiled for previos versions, classes can't just stop
working, at least not until they have been obsolete for some version updates.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espańol : http://asp.net.do/foros/
===================================
"Göran Andersson" <gu***@guffa.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl. ..
Actually System.Net.Mail replaces System.Web.Mail, which is now marked as obsolete.
>
Henning Krause [MVP - Exchange] wrote:
>Hello,
>>
>in .NET 1.1, only the System.Web.Mail was available. This implemenation had fundamental
>flaws. For example, attachment could only be added from files, not from Streams.
>>
>The .NET 2.0 implementation is System.Net.Mail and is much more flexible and has a richer
>featureset.
>>
>Best regards,
>Henning Krause
>>
>>
>"Frank" <fr*****@gmail.comwrote in message
>news:11*********************@n59g2000hsh.goog legroups.com...
>>Hi,
>>>
>>I am hoping to find out the differences between the
>>System.Net.Mail and System.Web.Mail.
>>>
>>Can some nice folks post the differences; or some urls which show the
>>differences?
>>>
>>Great Thanks
>>Frank
>>>
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____
http://www.guffa.com
--
Göran Andersson
_____
http://www.guffa.com This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Trond A. S. Andersen |
last post by:
Hi, all!
I'm trying to use the System.Web.Mail. "package" combinded
with System.Web.Mail.SmtpMail in order to send MS Excel
spreadsheets attached to mail messages. However, sending
one single...
|
by: clevrmnkey |
last post by:
I've had nothing but trouble from the System.Net.Mail objects, but I
finally need to make them work, and I can't for the life of me see what
I'm doing wrong.
I pared back my mail transaction to...
|
by: Frank |
last post by:
Hi,
I am hoping to find out the differences between the
System.Net.Mail and System.Web.Mail.
Can some nice folks post the differences; or some urls which show the
differences?
Great Thanks...
|
by: nudrat |
last post by:
Hi,
My requirement are :
1) In one PC in LAN Linus is installed which is used for net surfing.... rest of the systems have xp including exchange server.
2) We want to convert all email...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
| |
