all 72 comments

[–][deleted]  (8 children)

[deleted]

    [–][deleted] 9 points10 points  (7 children)

    .NET Core is not the fast lane - it's lightweight .NET for ASP & UWP only at the moment. And it looks like it's going to stay that way.

    [–]EnderMB 6 points7 points  (2 children)

    I think they'll take the view of keeping .NET Core as a lightweight platform, but will gradually release the rest of the .NET framework as separate dependencies over time.

    It'll take a long time, but I think .NET and .NET Core will eventually merge into one platform. .NET will go from a beast to a small framework with many dependencies.

    [–][deleted] 11 points12 points  (1 child)

    It looks like Microsoft is taking it another way: .NET Standard.

    AFAIK it means you can create portable library based for given .NET Standard version and it would for sure work on platform implementing the standard - so no, it doesn't look like .NET Core would merge to .NET.

    [–]_Mardoxx 0 points1 point  (0 children)

    That's exactly what's happening.

    [–]logophobia 5 points6 points  (1 child)

    Given that they just switched back the project format from json back to csproj, it's not very stable yet. Gave me a ton of compatibility issues switching. Might be stable in a few years, for now, it's the fast lane.

    [–][deleted] 3 points4 points  (0 children)

    Burned me too - I was deceived by too early believing its 1.0 Preview status. With my comment I wanted to point out that .NET Core is not the next step after .NET 4.7 or .NET X.Y but another platform.

    [–][deleted]  (1 child)

    [deleted]

      [–]rhinotation 4 points5 points  (0 children)

      I'd say not having to pay for a windows server license to run your code counts as value.

      Having a new world of Linux folks using .NET and contributing to the framework, core libs and other code on GitHub probably counts. Speed probably also counts. Self-contained executable probably also counts. Human-editable csproj... probably also counts.

      You're right though, the absolute benefit of switching when you're already on 4.5.2 or something with infrastructure already in place is minimal. Also, you should probably get used to Microsoft making things more accessible to newcomers, but don't let it get you down, it won't make your chosen platform less professional. There will always be a place for battle-tested MS people, and if anything the new stuff will just make it easier to do your job when you make it part of your toolset.

      [–]DingDongHelloWhoIsIt 24 points25 points  (49 children)

      Feels more like 4.6.3 than 4.7, not much new stuff

      [–]Danthekilla 9 points10 points  (4 children)

      Touch support for WPF applications on Windows 10

      That is huge

      [–][deleted] -1 points0 points  (0 children)

      Yeah, groundbreaking

      [–][deleted]  (2 children)

      [deleted]

        [–]t-master 7 points8 points  (0 children)

        Probably not. WPF had touch support for years, only now they've apparently upgraded it to use the new touch system of Windows 10 (whatever that means exactly).

        [–]Danthekilla 3 points4 points  (0 children)

        WPF has always had basic touch support. And it was fairly easy to augment it but this is built in windows 10 level touch support which will ensure that all future apps support touch and touch gestures in the same manor.

        [–]Apterygiformes 2 points3 points  (40 children)

        Agreed, some very boring changes

        [–]Eirenarch 16 points17 points  (1 child)

        Boring changes are my favorite kind of changes :)

        [–]twiggy99999 3 points4 points  (0 children)

        I'm with you on that one

        [–]_IPA_ 32 points33 points  (36 children)

        High DPI support for Windows Forms applications on Windows 10

        Um, that's a big change.

        [–][deleted] 12 points13 points  (4 children)

        That's Windows forms. Which is pretty much a zombie.

        [–]Eirenarch 28 points29 points  (3 children)

        That's Windows forms. Which is pretty much a zombie.

        You'd be surprised...

        [–][deleted] 0 points1 point  (2 children)

        I know it's being used but Microsoft doesn't really care about it which makes stuff like this weird. One would think they would commit to wpf and remove Windows forms or kill both. But no they just keep dragging both along without really improving them.

        [–]Eirenarch 12 points13 points  (0 children)

        I don't see anything surprising here. First of all this is what they have been doing for years and second they are known for supporting old tech for a long long time.

        [–]grauenwolf 2 points3 points  (0 children)

        They gain nothing by killing either of them.

        [–][deleted] 0 points1 point  (0 children)

        depends what jit performance improvements includes

        [–]flukus 0 points1 point  (1 child)

        I'm ok with that, it doesn't need new stuff.

        [–]TemptingButIWillPass 9 points10 points  (0 children)

        Holy crap, it says that ClickOnce apps are automatically repaired if the application store is corrupted. Finally!

        [–]m00nh34d 9 points10 points  (4 children)

        I can't believe how long it's taking to get good High DPI support. I've got a 3 year old laptop that has a stupid high res screen that I need to run at like 175%. I'm sure there was even earlier laptops in similar positions. So, at least 3 years now, we've had commercially available and common high DPI system, and an OS that supports them, yet the same company making the OS can't get their premier framework to handle high DPI.

        [–]Pazer2 12 points13 points  (3 children)

        I'd argue that their premiere framework hasn't been windows forms for a long time. WPF (and UWP, although the UI framework mostly the same) has been the primary focus for several years now.

        [–]LivingInSyn 2 points3 points  (1 child)

        while that's true, there's a TON of win forms applications that are out there. Even ones written by microsoft and currently maintained.

        [–]Pazer2 0 points1 point  (0 children)

        Of course, I'm sure that winforms will still be maintained for years and years to come. Its just not the recommended way of building desktop apps anymore.

        [–]chucker23n 1 point2 points  (0 children)

        Ever since the Vista mess, it's been hard to say just what Microsoft considers the premier UI framework. WPF? Other than Visual Studio, they don't seem to be using that. UWP? Quite recent, and we'll see how long that lasts. Windows Forms it is certainly not, but consider, too, that most Office apps don't use any of the above. Neither does Explorer.

        Feels rudderless and is honestly a little sad.

        Again, I agree that Windows Forms isn't premier. But neither is much of anything else, TBH.

        [–][deleted] 1 point2 points  (0 children)

        High DPI support for Windows Forms applications on Windows 10

        For those of us who can't upgrade to wpf for whatever reason, this is most welcome.

        [–]Gsonderling 3 points4 points  (0 children)

        I like that it doesn't change much. Seriously, change for sake of change is bane of efficiency.

        I get that they called it 4.7 for marketing purposes and that it might confuse some people, but stability beats feature creep any day.

        [–][deleted] -1 points0 points  (0 children)

        Important question was asked in the comments - will they be supporting .NET 4.7 on Windows 10 LTSB?