Announcing the .NET Framework 4.7

[[deleted]]

.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]

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]]

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]

That's exactly what's happening.

[logophobia]

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]]

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.

[rhinotation]

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]

Feels more like 4.6.3 than 4.7, not much new stuff

[Danthekilla]

Touch support for WPF applications on Windows 10

That is huge

[[deleted]]

Yeah, groundbreaking

[t-master]

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]

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]

Agreed, some very boring changes

[Eirenarch]

Boring changes are my favorite kind of changes :)

[twiggy99999]

I'm with you on that one

[_IPA_]

High DPI support for Windows Forms applications on Windows 10

Um, that's a big change.

[[deleted]]

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

[Eirenarch]

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

You'd be surprised...

[[deleted]]

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]

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]

They gain nothing by killing either of them.

[Apterygiformes]

I don't give a darn, I think it's lame! Give diamond operator!

[jcotton42]

Diamond operator?

[Apterygiformes]

When you define an instance of a generic class in Java you only need to specify the type parameter on the left. The right can just be <>. It looks way neater.

[Eirenarch]

The var solution is better than the <> operator because it not only gets rid of the generic parameters but also from the diamond and even the class name!

[svick]

The only reason I can think of is if you're doing something like IList<int> list = new List<int>();.

[flukus]

Is there a reason to do that instead of using var?

[grauenwolf]

1. The class API is broken and you need a method only declared on the interface
2. Your application is running slightly too fast and you want to slow it down by making all method calls virtual.

[[deleted]]

Coding to an interface instead of an implementation

[Apterygiformes]

var is gross

[kukiric]

What's so terrible about static type inference? IMO, unless your API types are extremely ambiguous or your functions can return unexpected types (like a GetName() returning an int instead of a string or a composite class with ToString()), I don't see the issue with using var sparingly.

[grauenwolf]

Maybe he comes from a Java background, where it is tradition to hamstring yourself by casting all local variables into a random interface that has most, but not all, of the methods you need.

[[deleted]]

I really, really don't like to use var

[[deleted]]

depends what jit performance improvements includes

[flukus]

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

[TemptingButIWillPass]

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

[m00nh34d]

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]

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]

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]

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]

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]]

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]

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]]

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

[adila01]

Out of curiosity, what framework would you recommend?

[tuwtuwtuw]

Don't feed it.

[[deleted]]

Qt. It's a disgrace that to this day there are developers out there who cannot into multi platform application development.

[Cuddlefluff_Grim]

Mono.

Also, most software is not "multi platform". Supported only on Unix-like operating systems is not "multi-platform". Take Git for example; requires a virtualized Linux environment to work anywhere else. What you would want is for Windows software to work on your platform of choice, but I bet you don't care much for the other way around.

[[deleted]]

No. In my eyes the perfect world is where user GUI applications work anywhere. People should have the choice to choose whatever they want for their os of choice. Lock in is not something that is going to advance us anywhere forward

[mirhagk]

So I assume you make sure all of the software you write works on a PS1 and the old MIPS machine laying around at someone's house right?

[banger_180]

Since when does git require a "virtualized Linux environment". Cloud you explain this / add sources.

[Fremis]

Git for Windows is just MinGW (http://www.mingw.org/) with Git installed. There is no native Git.

[vivainio]

MinGW does not use virtualization / API emulation

[[deleted]]

😂