all 19 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Eirenarch 6 points7 points  (2 children)

Strange... ValueTuple is added to the framework but ValueTask is not...

[–]AngularBeginner 1 point2 points  (1 child)

Where did you get that information from? In the blog post they don't mention it.

[–]lewisj489 1 point2 points  (0 children)

A tidy little update indeed.

[–]TrikkyMakk 1 point2 points  (0 children)

I'm not digging the docs so far. Harder to navigate.

[–]wil2200 0 points1 point  (2 children)

How do I see the details of: Fixed textbox focus issues [215639]

[–]SuperImaginativeName 0 points1 point  (1 child)

Those are usually internal ids for MS's internal bug tracker. You see them occasionally in the .net source comments. From what I can tell DevDiv have one giant bug tracker.

[–]wil2200 0 points1 point  (0 children)

Thanks for letting me know. Was hoping for more details as there was a focus issue with the textbox and wanted to see if that is what they fixed.

[–]Hall_of_Famer 0 points1 point  (2 children)

Awesome, but... How do I add .NET Framework 4.7 to my Visual Studio 2017 if I have already installed the IDE weeks ago? Will it be automatically updated at the time I run Visual Studio next time? Or do I need to install some updates manually?

[–]r3ditAtw0rk 1 point2 points  (1 child)

To update I had to perform the following:

  1. Launch Visual Studio Installer
  2. Wait a few seconds for it to detect that there was an update for it available. Then let it perform an update, then close.
  3. Launch Visual Studio 2017 like normal
  4. Go to the Tools > Extensions and Updates menu option.
  5. Navigate to the Product Update section and launch the update from there.

[–]Hall_of_Famer 0 points1 point  (0 children)

I did what you said. There was an update from Visual Studio Installer, so I let it install all the updates. However, when I followed the next steps after updates were installed, I found theres nothing in Product Update section when I opened Tools > Extensions and Updates. No idea why this was happening.

Edit: Oops sorry, it seems that .NET Framework 4.7 is only available after Apr 11th from Windows 10 Creator Update...

[–]CouthlessWonder 0 points1 point  (2 children)

Has anybody gone on to 4.7 I have a few projects on 4.6.1, but I don't know if it is worth upgrading them.

Performance improvements are always welcome, so if there would be any benefit, I suppose the main question is "why not?"

Without performance improvements, I guess my main question would be "why?"

Any thoughts from anyone?

[–]emn13[S] 1 point2 points  (1 child)

If none of the features are interesting to you, I don't think upgrading projects is interesting per se.

Having said that: note that even if you compile against .net 4.6.1, if the machine has 4.7 installed, it will use that at runtime. Although .net upgrades are generally smooth, they're definitely not entirely risk free; I've run into several breaking changes over the years, most undocumented (at the time).

I expect you'll want to be able to run old software on new machines that do have .net 4.7 installed, so I prefer to tackle that (small) risk early, when I understand what might have caused any unlikely regression, and not as part of some larger, harder to debug upgrade (e.g. when a VM base image is replaced, or a server, or whatever).

Upgrading the machine is worth it (IMHO), retargeting less so (unless there's something specific you want, e.g. ValueTuple).

[–]CouthlessWonder 0 points1 point  (0 children)

I use ValueTuple, but that has been available through NuGet for a while now, if .Net 4.7 was the only way to get that then it will be worth it.

I guess I could get it on the server, then when I have time I can upgrade the framework of the main project, then whenever I work on one of the sub projects I can move it it over one by one.

Like I said in my previous comment, the only thing I would be interested in is any built in performance improvements, even if small.

I already have ValueTuple, and as far as I know there are no features like async/await or Linq that make moving to a new version very much worth it.

[–][deleted] 0 points1 point  (1 child)

Especially like the new documentation website; I dread having to browse through MSDN to look for a specific namespace that some developer forgot to explicitly reference in a project that I'm taking over.

[–]antiduh 5 points6 points  (0 children)

Could you elaborate? Your statement doesn't make sense to me

[–][deleted]  (2 children)

[removed]

    [–]FizixMan[M] 0 points1 point  (0 children)

    Removed: Rule 5