xsharp.eu

Hello,

the Windows 10 Creators update introduces .NET Framework 4.7:

https://blogs.msdn.microsoft.com/dotnet/2017/04/05/announcing-the-net-framework-4-7/

There are two news I find particularly interesting:

• High DPI support for Windows Forms applications on Windows 10
• Touch support for WPF applications on Windows 10

And there is a new search facility for the .NET framework:

https://docs.microsoft.com/dotnet/api

Wolfgang

P.S. this .NET framework API will be replace 4.6 on all supported platforms, so we can expect these functions also on Windows 7 and Windows 8.1

After my experience with Visual Studio 2017 which doesn't even finish installing - for many users including me I don't especially looking forward to the next W10 update.

Microsoft is not good in releasing (reasonably) trouble free products. Even after extensive test rounds (like the W10 Insiders Preview, these fail on very basic points. The VS errors I got can be found in the RC comments from November 2016. A half working Visual Studio 2017 is not a big problem; I de-installed it and still have a working VS 2015. But a half working W10 Creators Edition is a big problem. We all know what happened with the first Anniversary Edition - just search a bit on that.

I have disabled my Windows Update Process; a very effective way to postpone updates in every W10 version. I will not enable it again until after a few months. It will at least postpone the increased telemetry to Microsoft and the new advertisements (Adds in Explorer for example, which you can shut up with disabling ‘Show sync provider notifications’)

The current W10 releases surfaced another problem. Every major release has new SDK code. If I want to make a W10 app now to play music for example, the Anniversary version has more efficient way to do that than the version before. But if I would use that, it only works on the Anniversary version. Currently still 20% of W10 versions do not run the Anniversary version. Partly because of deliberately delaying it, partly because W10 simply doesn't update - the update process is as sloppy as the rest of the programming. When we create something using "classic' Windows programming, like an X# or C# program, it works back to Vista or maybe even XP. But with this policy W10 app development is very discouraging - you may very well end up with an app which half of the W10 users can't run. And above that W10's market share is still below that of XP.

Dick

The main change in the Anniversary Edition was that users can no longer get rid of the totally unnecessary Lock screen, yielding many likewise unnecessary clicks. None of the bugs and unpleasantries were solved. So I expect it will be the same with this Creators Update. If you don't use Cortana, Edge (but Firefox instead), the W10 Start menu (but the Classic Start menu instead) there's not much you will miss, except -no doubt- some nasty features, I expect more advertisements and pushing to use Microsoft products.

Sorry to spoil the party, but I think that postponing the Creators Edition as long as possible will be wiser than getting it today....

Hi Dick,

I have updated now most of the PCs in my office (I'm missing only one), and this update was faster and easier than the update to the Anniversary update.

If I look af back at the XP fiasco, I see the decision of Microsoft to keep Windows 10 up-to-date as a very good decision, and I think this decision will save a lot of money (at least in my customers range): no more need to change machines because of a OS upgrade.

Of course, Microsoft has to refine the upgrade, but they have learned from version to version, I think.

Wolfgang

Dick,

I have also seen occasions where updates break things. With Ms, Apple even with X#. However my experience is that it usually better to update than to wait.
In most cases there is a good reason for an upgrade.

And I am glad that a new update has new SDK code. If Ms would not distribute the new SDK code then how would we be able to create apps that recognize and work with the new versions of the OS?

What I personally see as the wrong approach is the approach from Google and Samsung where old phones are not updated. Customers are left with an older phone with an older version of the OS() with known (security) issues.

Robert

My experience is the opposite. The last and probably only time I had a PC virus is 5 years ago I think. The last time we had a problem (not on our PC obviously) with a Microsoft update was a week ago where a clients' very large spreadsheet suddenly hung on loading. We received the spreadsheet and the plan was to see if I could read it in Excel 2003. In the meantime Kees discovered that it was due to a MS update - a patch (manual download) was supplied in the meantime.

I think all Windows major updates brought problems costing me a lot of time - and I also think every major update version is worse in terms of user experience; I gave the lock screen as an example. Totally unnecessary so which Microsoft idiot orders the option to skip the lock screen to be deactivated one wonders? Unfortunately you can not receive safety updates only without unwanted Anniversary or Creators updates in which case I think I am better of at least postponing all updates as long as possible. Basically I have the same with Office: Office 2003 does not receive updates anymore but it's much better in almost every respect than Office 2016 which I also have on this PC. The only reason I keep 2016 installed is that I sometimes had issues with opening docx/xlsx files in 2003; no doubt caused by updates Office 2007+ versions causing this because it used to work fine.

When we solve bugs or make improvements I usually have an idea which clients benefit and inform them separately. I usually see that clients never update themselves although in our software it's an easy procedure and I think that as long as they don't need improvements or fixes it's fine.

Hi Robert, Wolfgang, Dick, and all,

Like Robert, I have a policy to always update / upgrade to the latest version - of anything, O/S and applications. I learned this from a session at DevFest (London) many years ago and have stuck with it since then. I may even have been listening to Robert, as he was always there in the Crowne Plaza, and always passed on good tips.

Anyway, this policy seems to serve me very well, just the odd glitch or two over time. Also I find that by reporting any issues back to the Third parties concerned, they usually listen and respond accordingly - YES, even Microsoft. Insiders have a way of reporting back to those who wish to hear.

However, my success also may have to do with some other good advice from years back, and that is for installs, let the installer 'have its head', let it do what it wishes to do, as far as folders and default paths etc. are concerned. This could be as much a part of my general success as keeping up to date!

Oh! and as far as 'Win10' is concerned I have platforms of Desktop, Laptop, and Tablet - all kept up to date - however Julie's Tablet is not registered as being part of the Insider programme, I just keep it up to date with general public release updates etc.

Now then, if anyone is interested, I am currently communicating with 'TechSmith' and Microsoft over a rare issue that arose a couple of days back. SnagIt (11, 12, or 13) do not work properly with Win 10 build 16170, and possibly the version Wolfgang was talking of very recently.

I will keep you posted on any progress, as at the moment I can't capture screen content, and/or see previous captured images. Which means I can't make my eNotes. BUT - all is already completed for Cologne, so no issues and problems there ;-0) Oh! and Snipping tool still works - but is not in the same league as SnagIt, which is quite brilliant. And using SnagIt was a good tip from Paul Piko, many years back.

So to summarise, I go with Robert - always keep up to date as much as possible, and as soon as possible.

I like the new Visual Studio installer from this point of view, as we all can get updates to the VS version we are using, much easier than before.

Regards to all,
Phil.

Hi Phil,

the current production release of Windows 10 is 15063 - the Creators update.

Build 15070 AFAIK is the current release in the "fast ring" of the insiders builds.
I have used insider builds (on a test machine) before Windows 10 became ready to be prepared, but I would never use such a build on one of our production machines.

Snagit 10 works well on build 15063.

Regarding lost time: normally I start the montly updates only when I don't need my PC for at least 30 minutes, and for this major update is was the same: I started it before a longer break (I have upgraded the work PC of my wife/business partner this night, and when she needed to work with it today it was ready). It is all an issue of planning.... even in our small environment.

Wolfgang

P.S. I'm using a Google Nexus as mobile phone because they are upgraded for at least 3 years - so I'm one of the relatively few having Android 7.1.1 with patch level march 5, 2017, and for sure the next update will come in the next 2 weeks

Hi Wolfgang,

In that case it is versions after 15063 which suddenly caused Snagit to go wrong.

My reports have gone in to TechSmith and Microsoft.

Because I am not tied to customers demands on a daily basis any more, I can afford myself the luxury of the Fast Insider track, and trying to get any issues put right before MS publically release a new version. After all, if nobody finds and reports the issues, then they will creep into public versions. I bet a few of you guys expect you users to report back (immediately?) any problems they have with your software ;-0)

Oh! and don't tell me that your software does not have any issues, ever !

My 3.5 cents worth,
phil.

Hi Phil,

Because I am not tied to customers demands on a daily basis any more, I can afford myself the luxury of the Fast Insider track, and trying to get any issues put right before MS publically release a new version. After all, if nobody finds and reports the issues, then they will creep into public versions.

of course! But since I have not the time for it, I have decided to not use Insider builds anymore.

Oh! and don't tell me that your software does not have any issues, ever !

I would say more likely that a software without any issue is not possible (at least I say that to all my customers) - and if no issue is known, the it is because nobody has found anyone, and not because there are no issues at all.

I don't know many professions where such a small error like a dot instead of a comma can have cause such catastrophic errors like in programming.

Wolfgang