The build up to Microsoft's Build 2013

The build up to Microsoft's Build 2013

Summary: Microsoft's Build 2013 developer conference is just a week away. What's likely to be on the agenda?

SHARE:

In just over a week, Microsoft will be convening its Build 2013 developer conference.

build2013topics

Company execs have said to expect information of interest to developers across most every major product family: Windows, Windows Azure, Office 365, Windows Phone, Xbox and Visual Studio during the conference. But, with the launch of Windows 8.1 and Windows Server 2012 R2 public previews on day one, June 26, this year's Build will focus primarily around the next version of Windows, and to a somewhat lesser extent, Windows Azure, my sources have indicated.

Microsoft officials still aren't sharing information about who will keynote Build on Days 1 and 2, what kind of content will be featured in sessions, or how many attendees are expected for the three-day confab. (This year, Build will be in San Francisco, the first time Microsoft has held a major developer conference there since 1997.)

But company officials were willing to set the stage for Build via a phone conversation late last week.

Microsoft is reaching out to two main audiences this year at Build, said Steve Guggenheimer, Corporate Vice President of Microsoft's Developer and Platform Evangelism Group: The existing Win32, line-of-business/commercial developer community and the startup community. "We need a good conversation with that community," said Guggenheimer about the existing .Net developer base, many of whom have felt disenfranchised by Microsoft's recent developer push toward HTML/JavaScript.

"We haven't done a good job telling the .Net developers we haven't forgotten them," Guggenheimer acknowledged. "We need to tell them that."

Guggenheimer, unsurprisingly, wouldn't talk specifics about what new products and technologies Microsoft plans to announce at the show. When I asked whether Microsoft would be providing attendees with code or at least information about some kind of Xbox One and/or Windows Phone Blue software development kits (SDKs), Guggenheimer declined to comment. He did say Microsoft's message will be a furthering of what officials started detailing last year regarding the benefits of an increased amount of shared/common code across the guts of its key products.

"We will not be making a sharp turn. We will show how strong the bridges are" between Microsoft's various product families, Guggenheimer said. "We want to show people what's possible, going cross-platform."

Reading the Build tea leaves

That's all Microsoft officials are saying right now about Build 2013. But there are a few additional hints and tips worth passing on.

We do know that a first public preview of Visual Studio Blue, a.k.a. Visual Studio 2013, should be available in conjunction with Build. One would assume the next VS release would have more features to simplify and improve the development of Windows Store/Metro-Style apps, since that's what Microsoft wants and needs developers to build.

I'm curious whether the Bing AppEx team — the group that built some of the nicer apps for Windows 8, including Weather, Travel, Sports and new cooking/recipe and fitness apps — will field an SDK, too. According to a recent Microsoft job description, the AppEx team is building a framework for the development of Windows Phone apps.

On the Windows 8.1 front, there seems to be little left to announce about the OS update itself, given all the leaked builds over the past few months, coupled with Microsoft's own disclosures about many of the coming features. Over the weekend, the Windows team turned on the new Windows Store experience, so those with existing leaked builds can see the new look and feel of the Store plus some of the updated Microsoft apps that are part of 8.1.

The Windows Phone team, which is dependent on the Windows core, is still working on delivering smaller, incremental updates to the Windows Phone 8 operating system. A "GDR3" build is expected to arrive this fall around the time that Windows 8.1 is made available. Windows Phone Blue is expected about six months after Windows 8.1 is released to manufacturing, making disclosures (at least public ones) about the SDK for that release largely unlikely at the Build show.

Microsoft is known to be working to deliver even more common code across its phone, PC/tablet and entertainment console product lines. But that doesn't mean developers should expect a "write once, run on any version of Windows" experience to arrive in full in 2013. Unifying the app stores across these product lines also doesn't appear to be a 2013 thing, either, from what I'm hearing.

On the Xbox One front, Microsoft officials have said the company's new console operating system is actually three OSes in one. The "gaming" OS (residing in the "exclusive partition") is going to be where Microsoft-sanctioned third-party games will live. But Microsoft is expected to continue to gate which games will integrate with Xbox Live via a certification process, which means a "public" SDK for Xbox One doesn't seem like a 2013 deliverable. If Microsoft creates an app store for indepedent developers for Xbox One, that store won't be open for business in 2013, from what I've heard.

I'd think third-party SDKs, like MonoGame, Xamarin and PhoneGap, could get some play at Build, given Microsoft's planned cross-platform messaging. Windows Azure Web Sites, the hosting framework for Web applications and sites created using various languages and stacks (including a number of open-source, non-Microsoft-developed ones), may come out of preview soon as well and be a hot topic at the show.

Developers: What else are you expecting and hoping Microsoft talks up and delivers at Build next week?

 

Topics: Windows 8, Cloud, Software Development, Windows Phone, Windows Server

About

Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

48 comments
Log in or register to join the discussion
  • Haswell Surface Pro.

    Waiting to see it happen.
    ForeverCookie
    • Mary Jo, any word on this?

      I'm either really out of the loop or Microsoft is taking a page out of the Apple play book because I have not heard anything substantive on Surface Pro 2.
      alsw
      • Surface 2

        Hi. No... no word on when a new Surface is coming with Haswell... or any other processor. Surface team is continuing to decline to comment. All we know thanks to tipsters is an 8-inch Surface is supposedly in the works. No word on which processor or when it will ship. Rumor is later this year... MJ
        Mary Jo Foley
        • With MacBook Air Haswell Out - Microsoft Can't Wait

          My daughter has been using the new MacBook Air 13" for a few days, and the battery life is astounding. Easily 10+ hours of regular use on a charge (Office, surfing, Netflix, WiFi on). CNet reports 14:25, PCMag 15+ on video rundown tests. There is just NO EXCUSE to continue to manufacture the Surface Pro with an Ivy Bridge processor. I know I have been a severe critic/sceptic of Intel's battery claims for Haswell, but with an Air in hand, the proof is in the pudding so to speak. A 1.3MHz Haswell powered Surface Pro 2 should be priority one at Microsoft. Unless Apple has some secret sauce that Microsoft can't duplicate, an 8 hour Surface Pro is easily within reach.
          dksmidtx
          • MBA outdated non-IPS display, no Flash, downclocked CPU, bigger battery...

            Along with no touchscreen and semi-smooth scrolling, you can achieve long battery life with most modern CPUs.

            Just try mating a good display size of 1920x1080 IPS with an i7 Haswell and you have battery draining as fast as Ivy Bridge.

            Read the recent Verge article "Haswell Hype versus Reality":

            http://www.theverge.com/2013/6/13/4426360/massive-battery-life-killer-graphics-can-intels-haswell-deliver-on
            zambit
          • Agreed

            And a Haswell Surface Pro would help Microsoft enormously in enterprise environments, where there's increasing interest in the Surface Pro over iPads. The weight and battery life of the Surface Pro are the primary two factors holding it back, though. Haswell can help.

            What I'm NOT seeing interest in, at least in my own large enterprise, is an 8" Surface tablet.
            ParrotHead_FL
  • Restore System.Data to the metro .NET profile

    And make Compact SQL available.
    Mac_PC_FenceSitter
    • Yes...

      +1. The lack of DB stuff in Metro just means no business Metro apps.
      Asgardi
      • Well

        You could use Microsoft Access MDB still and there are few light weight DBs such as SQLite already available.
        Ram U
        • Re: such as SQLite

          Is Microsoft incapable of coming up with a serious alternative to SQLite?
          ldo17
          • Wow. You really are OCD in reference to MS, ldo17

            I realize that you're incapable of coming up with a serious post, but you just keep on hating and trolling, your fan base is waiting! :)
            William Farrel
          • You are more

            than 10 years out of date .... Microsoft has had alternatives for many years - I used to build Windows Mobile apps using Mobile SQL Server.
            roteague
          • Re: I used to build Windows Mobile apps using Mobile SQL Server

            Seems like it's now defunct: doesn't support Windows Phone.
            ldo17
    • Maybe System.RemoteData

      I understand that direct data access in WinRT would be a huge attack vector, but if a set of standard & hardened data services were easily hosted on a web or database server, and WinRT had companion API, then just maybe we can have our cake and protect it too.
      scH4MMER
      • Yep

        The big challenge is that there are certain objects in System.Data that you would want to return as a DataSet or DataTable (such as the return type of a SOAP or WCF service) where you have key relationships established, that you might then return for modifications.

        Being able to keep those "in type" would be ideal.
        Mac_PC_FenceSitter
  • do we have more information on IE10?

    do we have more information on IE11 and its developing for it.
    Mac_Win
    • IE11

      Hi, IE 11 is part of Windows 8.1. I'd think there will be dev guidance around it at the show... MJ
      Mary Jo Foley
      • uh no

        Nobody should be developing to a specific version of any browser. Ever.
        butter44
        • Why not?

          I largely agree, you shouldn't develop around a specific version of a browser, but as newer technologies become available in IE and other browsers, knowing what they are and how to use them is very useful to developers. I don't see where anyone was saying you should develop for one version of one browser here. Providing dev guidance on IE11 seems like it would be a wise move by MS. You may not want to implement things that aren't necessarily backwards compatible right away, but that is a whole other can of worms.
          Steve Steiner
  • Mini Surface

    Waiting for a low priced mini Surface. Also 1080p support for Windows Phone.
    OwllllllNet