Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Microsoft gives up: beat by lone dev

Microsoft gives up: beat by lone dev

Scheduled Pinned Locked Moved The Lounge
csharpasp-netdotnetvisual-studiocom
15 Posts 12 Posters 24 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R raddevus

    Yesterday I went looking for the old .NET SmtpClient class (allows you to send email messages) and landed on the official docs that warn that the class is obsolete. SmtpClient Class (System.Net.Mail) | Microsoft Docs[^] :wtf: Here's the top of the doc:

    [System.Obsolete("SmtpClient and its network of types are poorly designed, we strongly recommend you use https://github.com/jstedfast/MailKit and https://github.com/jstedfast/MimeKit instead")]
    public class SmtpClient : IDisposable

    I found this at stackoverflow: c# - Is System.Net.Mail.SmtpClient obsolete in 4.7? - Stack Overflow[^] It really went back and forth in the comments and answers : posters saying it is and isn't and it's a doc error and not a doc error and why is it in .NET Core 2.2 then? But there was an answer that said, "Microsoft says to use MailKit now..." Here's the github : GitHub - jstedfast/MailKit: A cross-platform .NET library for IMAP, POP3, and SMTP.[^] Maybe someone should re-write the System.IO libraries. ;P Pretty soon you wn't even download WinXYZ, you'll just pull a nuget library. :laugh:

    P Offline
    P Offline
    PIEBALDconsult
    wrote on last edited by
    #6

    raddevus wrote:

    I'm going to re-write the System.IO libraries tonight

    Be sure to add IReader, IWRiter, and IReaderAndWriter . I'm working on System.Diagnostics.Process . Anyone want to fix System.Console ?

    G Richard DeemingR O 3 Replies Last reply
    0
    • P PIEBALDconsult

      raddevus wrote:

      I'm going to re-write the System.IO libraries tonight

      Be sure to add IReader, IWRiter, and IReaderAndWriter . I'm working on System.Diagnostics.Process . Anyone want to fix System.Console ?

      G Offline
      G Offline
      GenJerDan
      wrote on last edited by
      #7

      And this Reader to Writer - McGuinness Flint - YouTube[^]

      We won't sit down. We won't shut up. We won't go quietly away. YouTube, VidMe and My Mu[sic], Films and Windows Programs, etc. and FB

      1 Reply Last reply
      0
      • R raddevus

        Yesterday I went looking for the old .NET SmtpClient class (allows you to send email messages) and landed on the official docs that warn that the class is obsolete. SmtpClient Class (System.Net.Mail) | Microsoft Docs[^] :wtf: Here's the top of the doc:

        [System.Obsolete("SmtpClient and its network of types are poorly designed, we strongly recommend you use https://github.com/jstedfast/MailKit and https://github.com/jstedfast/MimeKit instead")]
        public class SmtpClient : IDisposable

        I found this at stackoverflow: c# - Is System.Net.Mail.SmtpClient obsolete in 4.7? - Stack Overflow[^] It really went back and forth in the comments and answers : posters saying it is and isn't and it's a doc error and not a doc error and why is it in .NET Core 2.2 then? But there was an answer that said, "Microsoft says to use MailKit now..." Here's the github : GitHub - jstedfast/MailKit: A cross-platform .NET library for IMAP, POP3, and SMTP.[^] Maybe someone should re-write the System.IO libraries. ;P Pretty soon you wn't even download WinXYZ, you'll just pull a nuget library. :laugh:

        A Offline
        A Offline
        adudley256
        wrote on last edited by
        #8

        I had to upgrade to use Mailkit, SmtpClient doesn't support TLS1.2, so all of a sudden you can't send emails when your service provider decides to take security seriously.

        J 1 Reply Last reply
        0
        • P PIEBALDconsult

          raddevus wrote:

          I'm going to re-write the System.IO libraries tonight

          Be sure to add IReader, IWRiter, and IReaderAndWriter . I'm working on System.Diagnostics.Process . Anyone want to fix System.Console ?

          Richard DeemingR Offline
          Richard DeemingR Offline
          Richard Deeming
          wrote on last edited by
          #9

          PIEBALDconsult wrote:

          Anyone want to fix System.Console ?

          Miguel de Icaza is way ahead of you: GitHub - migueldeicaza/gui.cs: Console-based user interface toolkit for .NET applications.[^] There's also this .NET Foundation project, but it's still in alpha: GitHub - dotnet/command-line-api: System.CommandLine: Command line parsing, invocation, and rendering of terminal output.[^]


          "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

          "These people looked deep within my soul and assigned me a number based on the order in which I joined" - Homer

          I 1 Reply Last reply
          0
          • R raddevus

            Yesterday I went looking for the old .NET SmtpClient class (allows you to send email messages) and landed on the official docs that warn that the class is obsolete. SmtpClient Class (System.Net.Mail) | Microsoft Docs[^] :wtf: Here's the top of the doc:

            [System.Obsolete("SmtpClient and its network of types are poorly designed, we strongly recommend you use https://github.com/jstedfast/MailKit and https://github.com/jstedfast/MimeKit instead")]
            public class SmtpClient : IDisposable

            I found this at stackoverflow: c# - Is System.Net.Mail.SmtpClient obsolete in 4.7? - Stack Overflow[^] It really went back and forth in the comments and answers : posters saying it is and isn't and it's a doc error and not a doc error and why is it in .NET Core 2.2 then? But there was an answer that said, "Microsoft says to use MailKit now..." Here's the github : GitHub - jstedfast/MailKit: A cross-platform .NET library for IMAP, POP3, and SMTP.[^] Maybe someone should re-write the System.IO libraries. ;P Pretty soon you wn't even download WinXYZ, you'll just pull a nuget library. :laugh:

            T Offline
            T Offline
            Thornik
            wrote on last edited by
            #10

            Of course only time can show "usefullness" of the class and it's normal when you find "obsolete" of design which was done 10 years ago. BUT... why MS itself not fixing anything?? WHAT they are busy that they cannot rewrite one of most important classes? (be sure, mail notifications used everywhere!) MS can just make show how cool they are, "hard working", "hiring the best" and other BS. But reality shows they hire 10 indians for $100/month and do WORST code in the world. How long MS suppose to roll down??

            F 1 Reply Last reply
            0
            • Richard DeemingR Richard Deeming

              PIEBALDconsult wrote:

              Anyone want to fix System.Console ?

              Miguel de Icaza is way ahead of you: GitHub - migueldeicaza/gui.cs: Console-based user interface toolkit for .NET applications.[^] There's also this .NET Foundation project, but it's still in alpha: GitHub - dotnet/command-line-api: System.CommandLine: Command line parsing, invocation, and rendering of terminal output.[^]


              "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

              I Offline
              I Offline
              irneb
              wrote on last edited by
              #11

              Also stuff such as the good old NCurses ... but for DotNet: [GitHub - MV10/dotnet-curses: Portable cross-platform .NET Standard wrapper for the Unix ncurses library](https://github.com/MV10/dotnet-curses)

              1 Reply Last reply
              0
              • T Thornik

                Of course only time can show "usefullness" of the class and it's normal when you find "obsolete" of design which was done 10 years ago. BUT... why MS itself not fixing anything?? WHAT they are busy that they cannot rewrite one of most important classes? (be sure, mail notifications used everywhere!) MS can just make show how cool they are, "hard working", "hiring the best" and other BS. But reality shows they hire 10 indians for $100/month and do WORST code in the world. How long MS suppose to roll down??

                F Offline
                F Offline
                Fernando A Gomez F
                wrote on last edited by
                #12

                Thornik wrote:

                WHAT they are busy that they cannot rewrite one of most important classes

                Writing the next version of Metro/WinRT/UWP that nobody will use...

                T 1 Reply Last reply
                0
                • F Fernando A Gomez F

                  Thornik wrote:

                  WHAT they are busy that they cannot rewrite one of most important classes

                  Writing the next version of Metro/WinRT/UWP that nobody will use...

                  T Offline
                  T Offline
                  Thornik
                  wrote on last edited by
                  #13

                  hehe :) Yep! Well, they have not bad ideas in these products, but MS cannot follow idea where it suits - they always go to extreme case and... lose. I wish I have UWP, but not under Windows-Spy-10. And separate OS for mobile world also could be nice. Seems programmers give ideas to the top management, but tops are so stupid that bloat any idea till marasmus level.

                  1 Reply Last reply
                  0
                  • A adudley256

                    I had to upgrade to use Mailkit, SmtpClient doesn't support TLS1.2, so all of a sudden you can't send emails when your service provider decides to take security seriously.

                    J Offline
                    J Offline
                    Jan Hansen
                    wrote on last edited by
                    #14

                    You can set this somewhere to use TLS 1.2 with SmtpClient (works for me):

                    System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

                    1 Reply Last reply
                    0
                    • P PIEBALDconsult

                      raddevus wrote:

                      I'm going to re-write the System.IO libraries tonight

                      Be sure to add IReader, IWRiter, and IReaderAndWriter . I'm working on System.Diagnostics.Process . Anyone want to fix System.Console ?

                      O Offline
                      O Offline
                      ormonds
                      wrote on last edited by
                      #15

                      Let us know when System.IO.MindReader is done.

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups