Steve “Guggs” Guggenheimer is the Corporate Vice President of Developer Platform & Evangelism and Chief Evangelist for Microsoft.
Learn more about Steve.
Last month we announced that Build 2014 will be back at the Moscone Center in San Francisco, April 2 – 4. Hopefully you’ve saved the date on your calendar, because registration is now open at www.buildwindows.com!
Build is our premier developer event, targeted at people who want to create experiences that span PC, tablet, phone, console, server, and cloud, and at this year’s event we will share what is coming for Windows, Windows Phone, Windows Azure, Windows Server, Xbox, Visual Studio and more. Perhaps even more importantly, we’ll be talking about what Microsoft is doing to protect your technology investments, regardless of their form: tools, skills, language preferences, code, and apps, to name a few. One of the key ways we’ll do this is through client platform convergence around a common core – spanning the application platform, browser platform, apps, and APIs – in a way that makes it easy to reuse your skills and existing code. This means it will be much easier to build one app for all Windows devices while at the same time having the ability to take advantage of device-specific capabilities across form factors, screen sizes, and local hardware functionality.
We’re excited to share our progress and how the strategy is continuing to evolve, creating even greater efficiencies and of course, opportunity, which is what Build is all about.
We’ll share more in the coming months, but know that Build is a can’t miss event for anyone who wants first hand access to what’s coming next from Microsoft.
Get yourself registered today!
Hi Steve - thank you for the update. I would like to put in an impassioned request for one change in how Build has operated in previous years. With the live-streamed keynotes and 24-hour streamed sessions, the value-proposition (and manager cost justification) for a conference like Build skews heavily towards Networking. However, Build seems to have pursued a "secret schedule" approach over the last few years, not even publishing details about the non-session evening activities until the conference actually begins. This approach hamstrings vendors' abilities to plan and book events that serve as crucibles for the conference networking. I realize that there is some tension that drives the need for some confidentiality in the scheduling, but would it really hurt to publish the skeleton of the overall conference schedule, as well as a complete view of the evening events?
I'm in agreement with John Garland. While our office has a conference budget, Build is a hard-sell to our managers without a pre-announced schedule (even if it's a little obfuscated). I've been trying to get approval for Build 2013 and Build 2014 without success, but I can only hope that Build 2015 will give me more ammunition with which to present my case. I've also tried pointing backward to schedules from previous years as examples, but upon seeing the sessions available online, I have also had to promote the Networking angle of the conference.
I'm with the other comments on this. I attended Build 2014 and it was a slap in the face (and wallet) that there was only one person (Chris Anderson) who could speak intelligently about the WPF and the needs of Desktop developers and the only answers we could get are "we hear you". My trust is very low at this point and I just don't see the value proposition in attending.
MS really needs to focus on having useful sessions developers care about at this conference. I've attended the last two, and although I really enjoy the announcements, the lack of a schedule beforehand is problematic. The lack of schedule and often lackluster sessions left me with the impression that the event was thrown together at the last minute.
For instance, I attended a session last year about the new features in Visual Studio, and the presenter didn't even know about the async debugging or return value capture features for .NET- I had to find out from reading concurrent blog posts online, and the presenter was surprised when I brought up the features to her.
I hope you guys put more effort into making something really useful this year, in addition to the usual announcements. Your customers want more focus on the desktop and server-side, and a lot less focus on building Windows 8 apps, which is clearly not where most of your customers lie.
That all being said, I'm really hoping to hear Anders talk about the future of C# and TypeScript at this year's conference!
First, let me know say thanks for the comments, appreciate your feedback. On the schedule, quite frankly, we are still building it out as we are still a few months away. That said, we hear your feedback on the schedule, especially around the evening events and as we share the block of times for the sessions, we’ll look to include that for evening events as they get locked in. While I can’t make any hard commitments, we are working hard on the content, taking your feedback and ensuring we are delivering a great event.
I’m truly excited about Build and am hoping to see you there.
Thanks for the reply Steve. One of the tough things about feedback like this is that it is hard to know how to direct it to the proper place. These events aren't trivial to pull off, and there's a lot of moving parts and bodies involved. I appreciate your having taken the time to reply, your acknowledgement of the concerns, and any efforts you are able to make toward their resolution.
Now, can we talk about the West Coast bias? (j/k)
Windows 8 was fine without the Start button! It was a crutch! And will always be. In the next version of Windows, allow the user to press the Windows Key+M (for Metro) to offer a semi-transparent tile list of application. Do not bring back the Start Button or Start Link! People unable to accept the new change should be forced back to Windows 95!
Also, in the next release be truly free of any backwards compatibility! Remove alphabet drive dependency and start using Containers for all objects (drives, input, output, etc.). The backslash should never ever again be used to specify the location of a folder from a command or address prompt.
AND DON'T BRING BACK THE START BUTTON!
@Watson Prunier, SOC - The Metro Interface is the absolute worst interface I've experienced in 30 years... the flatness is a horrible design concept (early MTV anyone), the no-contrast VS mess, the let's jump on the non-existent need to have a tablet/desktop hybrid OS... Not only do I hope they bring back the Start Menu, I hope they realize that if you do real work on any device with large numbers of programs (& versions of programs) menus with the ability for static locations allows for much faster access & better organization than swipe to infinity or type in a search box to find stuff... not to mention having oh I don't know, "windows", for accessing multiple programs at the same time (what a concept Windows 8) is better.