The Microsoft Build 2017 Recap: What To Expect When You’re Expecting Windows
by Brett Howse on May 19, 2017 8:00 AM ESTFirst Thoughts
Build continues to be one of the most important events for Microsoft for the year, and this year there was plenty of announcements for what’s coming this year for Windows, Azure, and more. There are plenty of chances for developers to make their impact, with a surge in computing devices available now. Phones, PCs, tablets, Xbox, IoT, and other devices are permeating the world we live in, and Microsoft is hoping to not only provide devices, but to also power cloud connections through Azure, and they continuously update their tools to enabled developers to do more.
On the Windows front, there is plenty to look forward to this year. The Fall Creators Update is going to bring some excellent additions to Windows, after the Creators Update which just came out was a more muted release. OneDrive Files on Demand, Linux Subsystem updates, and more apps finding their way to the store thanks to the help of the Desktop Bridge for Windows should provide pretty much anyone with something to look forward to.
Microsoft also announced quite a few updates to their developer tools, and they continue to expand their cross-platform capabilities after the purchase of Xamarin last year. Visual Studio Mobile Center was announced, Project Rome to add the Microsoft Graph to apps, and a Xamarin Live Player was announced which lets you deploy, run, test, and debug iOS apps from a Windows PC.
Windows is not the dominant platform it once was, but with Azure, Office 365, Microsoft Teams, SharePoint, and more, Microsoft still has plenty of platforms to target. Windows has a diminished role in the world of 2017, but Windows 10 is running on over 500 million devices, and if Microsoft can ever get developers to embrace the store, they should have an easier time in the future with updating the base frameworks.
This looks to be another exciting year to keep track of what’s coming out of Redmond.
Facebook
Twitter
RSS
85 Comments
View All Comments
Gothmoth - Friday, May 19, 2017 - link
they should do proper testing of updates... one of the last updates messes with my audio system. :-(close - Friday, May 19, 2017 - link
The thing with "proper testing" is that unlike Macs for example Windows runs on thousands and thousands of different hardware and software (drivers especially) combinations. Proper testing on all of them is possible only theoretically.So MS figured out what they think is a way to get proper, real data from real computers to aid with troubleshooting and debugging (to which they added another level of data to aid their bottom line :D). They called it telemetry and we all know how people reacted to it.
Thing is if you want *your* system to be more reliable you have to send some reliability data to MS. Don't expect any magic though. There's a chance you have a uniquely non-standard setup.
raiden1213 - Friday, May 19, 2017 - link
How about the ability to NOT install certain updates. You know, like back in the windows 7 and 8 days?Forced updates are never a good idea for an operating system that runs on "Thousands and Thousands of different hardware"
close - Saturday, May 20, 2017 - link
Sure, then you get thousands and thousands of different update configurations. How does it help with testing when you have for example 200 updates available for an OS and everybody has a different combination applied? How do you make sure that every future update works for your combination?sallgeud - Monday, May 22, 2017 - link
That's how you end up with WannaCrypt, fool.mominusa - Saturday, May 20, 2017 - link
Well, five minutes on the internet would have let them find the "lose wifi on wake from sleep" bug that has driven me nuts. Another five minutes on the internet could have told them that the anniversary edition update brought it back and the workaround that solved it previously no longer works. I am sure they much have had thousands of feedback comments on it as well, and I personally sent several. They dont need "more data", they just need to resolve known issues.close - Saturday, May 20, 2017 - link
I hope you realize that's not how software development and debugging is done. Googling for a generic error that may or may not be a Windows issue or a driver issue. And I hope you realize that the people affected by this are a small fraction of the total number of Windows users. Everybody thinks their bug is critical because it shows up on the first page of Google but it's not.To prove a point, I searched for "Windows is great" and found plenty of happy people.
And reintroducing bugs is exceptionally common in software development. It's down to reusing old code. If you tell me what you do for a living I can find a problem that affects lots of people. And I'm pretty sure your work doesn't cover 80% of a market.
close - Saturday, May 20, 2017 - link
Anyway, how many such serious/obvious problems did you have with updates in the past 2 years? No software is perfect and if 1 or 2 bugs is all that you've encountered when updating such a complex piece of software like Windows, with all its dependencies on other software and drivers I'd say it's not that bad, is it?It's no different than any other OS, even those that run in very standardized configurations.
emn13 - Friday, May 19, 2017 - link
Same here - motherboard integrated realtek audio required a driver reinstall to work. The same driver that was already installed worked; so I'm guessing it was a config corruption issue.It's not the first time I've had issues with updates, but it's pretty rare all around, IMHO. I can remember maybe a handful of cases the past decade or so - not too bad, right?
Samus - Sunday, May 21, 2017 - link
I've come across a reproducible wifi bug in the Creators Update across different hardware: failure to "reconnect' when resuming from sleep, even though the connection shows you are connected to the wireless network, there is botched network connectivity; some works, some doesn't.Going back to sleep and resuming, or disconnecting and reconnecting, solves the problem in each case. Driver updates didn't fix the issue. All laptops with this issue had various Intel controllers, 7260's, 8260's, N's, AC's...could be an Intel issue, but it didn't happen before creators update.