back to article Compatibility before purity: Microsoft tweaks .NET Core again

Microsoft's open source fork of the .NET platform, called .NET Core, will be modified for better compatibility with existing applications, says Program Manager Immo Landwerth in a recent post. When the company embarked on its .NET Core effort, it took a minimalist approach, stripping out legacy code in order to get the best …

  1. Bronek Kozicki Silver badge


    So basically Microsoft are making an effort to make .NET Core attractive platform on Linux, also for migration of applications from Windows, by providing developers with access to basic APIs they are used to on Windows.

    Not trying to get into the motivation or future plans in regard to .NET Core on Linux (for what I know there could be many plans, any one opposing others), but the move is certainly interesting.

    1. energystar

      Re: Interesting

      Purpose is to lend a hand to old programmers.

      Those are not going to make the transcode.

      Expectation is to rescue Legacy, for the new programmers.

      For the new, or renewed Companies.

  2. J J Carter Silver badge

    The strategy is coming clear...

    Let devs port all legacy Win32 apps to Linux so Windows client isn't needed, ready to connect to SQL Server on Linux.

    1. Warm Braw Silver badge

      Re: The strategy is coming clear...

      Win32 apps are, by definition, pretty much "tied to a particular operating system implementation", so that definitely isn't the strategy. Being able to develop and deploy server/cloud applications for Azure without a Windows desktop running Windows tools definitely does seem to be on the roadmap, though, which seems like a sensible precaution given the state of the desktop market and the general loathing of Windows 10.

    2. Anonymous Coward
      Anonymous Coward

      Re: The strategy is coming clear...

      "ready to connect to SQL Server on Linux."

      That's only ever likely to be a development tool. If you want the fully featured product with clustering, etc. it's going to be on Windows. e.g. "Have a free version to develop on. When you out grow it, pay for the real thing..."

    3. Dan 55 Silver badge

      Re: The strategy is coming clear...

      That post would actually make sense... if Win32 and .Net weren't different APIs.

      1. Vincent Ballard

        Re: The strategy is coming clear...

        A lot of the .Net libraries are thin wrappers over Win32. That's probably why they talk about "not tied to a particular operating system implementation". E.g. half or more of System.Security.Cryptography will have to be removed, leaving only the XYZManaged implementations.

  3. steamnut

    Dogs breakfast

    So, rather than buy Sun with Java when they had the chance and not wanting to tackle the awkward-by-nature Oracle, Microsoft persist with this C#/.NET mess.

    The libraries are already large and now they are going to get larger as the real world problems of cross platform compatibility dawns on them.

    Clearly Microsoft sees Win10 as the end of the OS line and Linux has been deemed a better option despite their previous CEO slating it as the devil himself.

    Meanwhile C#/.Net is a development money pit until they have their next "bright" idea.....

    1. Anonymous Coward
      Anonymous Coward

      Re: Dogs breakfast

      "Microsoft persist with this C#/.NET mess."

      It massively outperforms Java and is far more secure though...

      1. Geoffrey W Silver badge

        Re: Dogs breakfast

        RE: "It massively outperforms Java and is far more secure though..."

        And its a much better designed language all round...Any more?...

        1. Law

          Re: Dogs breakfast

          It doesn't bundle the ask toolbar with the installer...

          1. Pig Dog Bay
            Thumb Up

            Re: Dogs breakfast

            And it has aqueducts!

  4. Barely registers


    FFS - hitting a moving project target is difficult enough without having the platform underneath you constantly moving as well.

    Can someone at MS just take a deep breath, step away from the kool-aid vending machine and damned well make up their mind what they're actually trying to do, and just deliver a stable platform please?


    1. GavinC

      Re: Agile

      That's why you wait until a platform is formally released before using it on projects.

  5. Michael Habel Silver badge

    Is there any reason to use this over gcc? Seems to me that gcc seems decent enough having used it to build my own customized build of CyanogenMod about a week back now.

    1. Paul Crawford Silver badge

      If you already have projects or code-reuse written in .Net or C# perhaps?

    2. This post has been deleted by a moderator

  6. bombastic bob Silver badge

    and the size of its system libraries will increase

    title = quote from the article.

    YES. That is the nature of Microsoft's bloatware known as ".Not" (aka '.Net').

    It's why I avoided doing anything with 'mono' whenever possible, back in the day when it was relevant. But in one case I was 'ordered' to do so by my boss at the time, who was a total C-pound and '.Net' fan, and wrote a C-pound GUI application to be used on Linux to test the system we were working on (yeah, it 'worked'). He also like Windows Vista over XP. And most of us were Linux+embedded people, doing kernel drivers. [he also thought that putting a linux VM on a Windows server box to run 'case sensitive' source control was a BETTER idea than dedicating a Linux machine for that same purpose]

    1. energystar

      Re: and the size of its system libraries will increase

      Who are at the controls -of this world- anyway? Please hide the lollipops .

    2. 1Rafayal

      Re: and the size of its system libraries will increase

      Someone doesn't know that Gtk# was the gui layer for mono at the time then, regardless of c# or not....

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2019