Microsoft shows off the next release of ASP.NET

Microsoft shows off the next release of ASP.NET

Summary: Microsoft is streamlining its ASP.NET server-side development framework with its next release, codenamed 'Project K.'


Microsoft officials is beginning to share publicly details about the next version of the company's ASP.NET, its server-side Web-development framework, on May 12.

At TechEd in Houston, Microsoft is showing off what officials are calling ASP.NET vNext, which was codenamed "Project K." Officials are calling this a "streamlined" and "cloud-optimized" version of .NET.

The Open Web Interface for .Net (OWIN) is "taking over" the ASP.NET runtime, said Jeff Fritz, an ASP.NET expert. ASP.NET MVC v.Next will be OWIN-compliant, which means ASP.NET will allow developers to assemble and build their applications using Web components, giving programmers access to a bigger and more flexible set of building blocks for their server-side apps.

At its Build conference in April, Microsoft announced that it was making ASP.NET one of its open-source contributions to the .Net Foundation.

At TechEd, Microsoft also announced that it is building into Visual Studio tooling for the Apache Cordova platform, which allows development of multi-device hybrid applications using HTML and JavaScript. The message is that Visual Studio developers have a choice: They can build native Windows, iOS and Android applications using either .NET and Xamarin, or opt for HTML/JavaScript using Apache Cordova. The Community Technology Preview of the Apache Cordova integration is available today.

Microsoft also announced the release to manufacturing of Visual Studio 2013 Update 2 at TechEd. Visual Studio Update 2 is a foundational piece of Microsoft's "Universal Apps" strategy. Using Update 2, developers can reuse more of their code when writing apps that will work on Windows 8.1 and Windows Phone 8.1. The company also announced today that it is releasing a set of application programming interfaces (APIs) and service hooks that integrate third-party services with Visual Studio Online.

Last week, Microsoft quietly rolled out .NET 4.5.2, which includes a number of bug fixes, security updates and "nominal" features, according to company officials. When Microsoft delivered .NET 4.5.1 last fall, officials said to expect the company to crank up the pace and make regular updates to .NET outside of major releases.

Topics: Mobility, Microsoft, Open Source, Software Development, Web development


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.


Log in or register to join the discussion
  • Deploy to iOS?

    Looks like I missed something along the way. Didn't Apple disallow third-party development tools at some point in time? I assume that has changed?
    • Yes, that changed a couple of years ago

      What Apple still enforces is that apps cannot dynamically generate code at runtime (i.e., no JIT) and that apps must be built and deployed (for testing, debugging, etc.) using Mac's.
      • There was a lot of blowback when they did that

        as torpedoing Unity and Xamarin would have cost the App store some of its biggest ticket items. They rolled it back within a few months once it became clear they were having to hold their nose and let a lot of that through anyways.
    • Things just do not add up

      So what is going to happen when Windows developers discover they can make more money deploying to iOS than to Windows? I just don't get it. Early signs show that MS' foundation technology, Windows, is in trouble, and MS is going around doing all it can to support competing technologies, in order to make some extra bucks. It is like having a pizza parlor, and deciding to sell your secret recipes, popular beverages, unique operation methodologies, etc. as services, to any and everyone who will buy them. Everything that makes your pizza parlor stand out from the crowd, you are putting up for sale. What on earth do you think is going to happen eventually? Your pizza parlor is going to be drained of all its uniqueness, and it's going to collapse. Has MS already decided that Windows is a lost cause, and that it has no choice but to divvy up the company's assets into services, to ride out the platform's inevitable collapse? This is how things seem to me, because the company's actions just do not add up. MS cannot both believe in Windows, yet keep doing all it can, to strip its major platform of its uniqueness.
      P. Douglas
      • iOS doesn't replace Windows.

        One is a mobile operating system, the other isn't.

        If Windows is a pizza parlor, then iOS is a snack stand that happens to sell hot pockets.

        Sure, they're cheap and they taste like pizza, but the pizza parlor sells actual pizza.

        You wouldn't feed your family hot pockets for dinner, would you?

        Hot pockets are good for breakfast and maybe lunch, if you're stretching it.

        There is plenty of good food to go around, and one does not have to replace another.

        Anyhow, the uniqueness of a pizza depends on who makes it. Besides, Microsoft isn't selling their secret recipes here, they're simply adding more ways to buy a pizza.
        • I'm still scratching my head

          I'm just confused. What I'm seeing doesn't make sense to me. Maybe I'm like Dr. McCoy on Star Trek. I'm just a simple country doctor, and I'm just not able to wrap my mind around what I'm seeing.
          P. Douglas
          • It makes sense.

            The strategy is the correct one. Microsoft has always worked to make the lives of developers easier. They started as a tools company and only became and O.S. company when DEC refused to work with IBM to deliver a Disk Operating System.

            Whoever can solve the multiplatform development problem, simplify the process consolidate the code base, and fix multi-store deployment issues (and also promote development for their own platform in the process) stands to win big in this new, fragmented future.

            As a developer who works with Microsoft Technologies, I whole heartedly support this move.
          • Digital Research not DEC

            I don't think they refused to work with IBM. By fluke, Gary Kildall just happened to by out flying a plane when they called. If my memory serves me right.
      • Microsoft is a software company and not a Windows company

        You've got to remember that while Microsoft's primary concern is Windows, they're first and foremost a software company. This means they need to be platform agnostic in certain instances. Office for iPad for example makes tons of cash from subscriptions. Why ignore such a huge market? So does applications like Visual Studio. If you're using Visual Studio, you're using Windows and most likely you're going to use SQL Server as your DB and host your services on IIS. Microsoft is keeping developers on the MS platform and allowing them to service their iOS needs at the same time. Ignoring them will mean that they'd just jump ship and have no way back to Windows. It's the same reason the iPod succeeded. If Apple never built iTunes for Windows, it would have failed. Failing to go cross platform can be backfire in certain instances.