What should you do with your .Net apps?

'The .Net Core has brought a renaissance in .Net,' says Scott Hunter, a member of the .Net engineering team. But that doesn’t mean you should port your existing apps

future of .NET apps

As web and mobile development have become increasingly important, .Net has faced an increasing amount of competition from open source platforms, as well as some confusion over its direction.

That wasn’t helped by problems in communication like when, some years back, a Microsoft executive announced in a rather off-hand way that Silverlight was dead. Or the lack of news about WPF for several years. Or even the way the WinRT framework in Windows 8 appeared to suggest that the .Net Framework was being superseded by “modern” apps.

To avoid such confusion, Microsoft clearly addressed any concerns about the long-term future of .Net when it made .Net open source and cross platform, as .Net Core. “These changes by Microsoft make investments in .Net even more valuable,” says Vassil Terziev, the chief innovation officer at Progress Software. “Businesses can now continue to develop in .Net without also being forced to run Windows in the data center. It gives .Net shops even more flexibility and control over their costs and deployments, while not forcing them to retrain their engineering teams.”

Still, .Net Core didn’t address one of the continuing problems: Microsoft kept bringing .Net to new platforms, but it was a slightly different .Net every time. “Moving forward, one of our primary goals is to unfragment .Net,” says Scott Hunter, a member of the .Net engineering team.

“We’re adding consistency to .Net. No matter where you are on the .Net continuum, whether you’re in the .Net Framework or in .Net Core, a huge, consistent piece of .Net will be exactly the same,” Hunter says. “There are the different app models like WinForms, WPF, Xamarin, ASP.Net and the Entity Framework, and then there’s all the .Net that's just generic. We’re going to take all that and wrap it into .Net Standard.”

That will make .Net code far more portable among Xamarin, UWP, .Net Core and the full .Net Framework. “If you write against .Net Standard, that's a contract saying it will run on Xamarin, on .Net Core and on the full framework,” Hunter says. It’s also where new APIs will be added, to make sure they’re available to .Net Core and Xamarin — and .Net Standard 2.0 will bring all the APIs that are in Xamarin and make them available in .Net later this year. “In the same timeframe, UWP apps will benefit from a bunch of APIs that were hidden from them,” he adds.

That consistency will make it easier to take advantage of the cross-platform options of Xamarin and .Net Core and keep .Net relevant to businesses.

The more familiar .Net technologies will keep getting new features too, Hunter says. “As far as their WinForms and WPF investments go, [businesses] should be feel comfortable that those are going to be great moving forward and will get new language features and new APIs. WinForms and WPF are still just as relevant today: If you're trying to build desktop apps, they are great frameworks. With Centennial you can take those desktop apps and take advantage of Windows 10 features like live tiles and desktop search — and you’ll continue to see us bridge some of those gaps as we move forward.”

Switching to .Net

All this means that existing .Net developers aren’t moving away from the platform, says Paul Veitch, senior director for technology services at managed services provider Avanade (a Microsoft joint venture with Accenture). In the last year, he says, he’s no longer hearing the old frustration that the Silverlight technologies they’d developed for were no longer going to be supported. Instead there’s a new sense of excitement.

Businesses who work with Avanade might be the least likely to move off .Net, but Veitch also notes the number of enterprises he works with who are switching to Microsoft and moving to .Net from other platforms.

“We see new customers coming from mainframes, from Cobol, from Java, from a plethora of other technologies, and having a Microsoft strategy. They need to figure out how to use it all, but there’s genuine excitement about what Microsoft is doing.”

In some ways, Microsoft’s new direction may make more sense to businesses that aren’t already using .Net. “Our clients are looking with some surprise at the Microsoft changes under Satya Nadella,” Veitch says. “The people who are still trying to digest that are customers that have been on the Microsoft platform for a long time. Organizations that aren't traditionally Microsoft customers are looking at what Microsoft is doing and seeing some radical new things happening.”

Some of the increased interest in .Net may come from uncertainty about the future of Java EE. Although Oracle has recently announced some of its plans for Java EE version 8, Veitch believes the lack of earlier information has caused concern. “The marketplace has been saying that perhaps Oracle is no longer actively developing Java, potentially causing people to think again about their investment in it.”

Those businesses don’t always point to the improved cross-platform support as a reason for the move and .Net Linux deployments aren’t yet significant, Veitch says, but he expects it to become more important over time. And .Net Core is more suited to new development than for porting existing apps, he says. “Businesses already using .Net are taking a watching brief around .Net Core. The level of maturity is good now but it’s a recent innovation and lots of things that have been around for a long time in .Net Framework aren't there yet. Porting a legacy app that’s been around for a number of years to .Net Core is difficult at this point. They’re definitely looking at it for new developments, rather than for porting applications wholesale.”

Interest in .Net Core is often tied to plans to use platform-as-a-service (PaaS) services on Azure, or containers and microservices, notes Veitch. “They’re looking at it alongside a devops and containerization strategy; they want to be able to develop .Net Core for a lighter footprint in containers.”

That was actually one of the goals for .Net Core, Scott Hunter points out. “We want to make sure .Net is an awesome platform for building containers and microservices. You will see us in future build frameworks on top of .Net Core specifically in the microservices world.” To make that work, even ASP.Net will become modular. “In the microservice world lot of folks try to make things as small and fast as possible. ASP.Net will be very small and very modular. If you just want something small without MVC, routing, controllers and so on, you can have that. You can use as much or little of the framework as you want. For the first time, we give you a dial and you can dial it down to nothing and then dial in as much on top as you need.”

Hunter has ambitious targets for how small the runtime can get in a container — at least three times smaller than options like Node and Java. “Our target is to be under 100MB for the runtime running a container for a microservice,” says Hunter. The Visual Studio IDE, which continues to be very popular in the .Net world, will also make deploying containers and microservices more approachable for .Net developers, he promises. “If you’re a container person, think how much work it is to set up continuous integration and continuous development and testing. When you want to move the container to the hub and publish it, there are a whole bunch of steps to set up. You can envision us making that three clicks and you're done, to get a full workload running on platform.”

Xamarin has been an important part of generating interest in .Net. “Most of the businesses I deal with treat iOS and Android as primary core platforms,” Veitch notes. “Xamarin had already got them excited and they got even more excited when Microsoft bought them because that made them feel they’d made a good strategic decision to pick up the technology.”

There’s less interest in porting existing iOS and Android apps to Xamarin and more in using it to build hybrid apps using a native container for HTML5 code. “They like the updateability but they recognize they can't get all the features, performance and behavior of native apps in HTML5. Using a native container and having HTML5 sit inside it means they’re not compromising on functionality. And they’re looking for applications that can adapt and deliver different capabilities on different devices and screens.”

Xamarin also solves the problem of what to do with any remaining Silverlight apps, Hunter says. “Either mobile or web would be the right direction to move with Silverlight apps. Xamarin is the easiest transition because it’s a fully managed stack and with Xamarin Forms you have a consistent UI that runs across iOS and Android.” In the future, Xamarin might even create UWP apps.

Like Veitch, Terziev says existing .Net developers view cross-platform development with .Net Core as a strong option for the future, but they’re not rushing to replace existing apps. “The .Net community is obviously much more mature now, and they’ve been around the block a few times with big shifts in .Net.

As a result, I think there is more of a cautious embracing of the bleeding edge coming out of Redmond. We still have customers happily extending WinForms and WebForms apps because those remain some of the most “drag-and-drop” friendly technologies born on .Net. The only Microsoft UI technology we’ve seen a wholesale switch from is Silverlight, and in those cases most developers landed in either HTML5 or back in WPF. We expect things like .Net Core to primarily show up in new projects where, in the past, technology decisions (like Linux servers) may have pushed a .Net team to consider NodeJS or Java.”

Open opportunity

A wide variety of services are adding support for .Net. “There are lots of libraries creating hooks into MVC and Microsoft technologies right now. There’s something of a head of steam building,” Veitch says.

There’s even a new set of .Net libraries for Google cloud platform services like BigQuery and Google Storage, and the IronPython project (Python for .Net) is restarting after a two-year hiatus. “Now that we’ve got a really open platform that runs everywhere, it's got all this interest,” Hunter explains. “The .Net Core has brought a renaissance in .Net.”

Having launched a Windows version of its open source database, RethinkDB has seen increasing interest from .Net developers, which community manager Christina Keelan attributes to the cross-platform promise of .Net Core. “People want to be able to develop in Visual Studio on a Windows desktop and deploy to Linux servers. RethinkDB's changefeeds, which allow queries to receive live updates, are particularly attractive to .Net developers who are building real-time web applications with ASP.Net and Microsoft's SignalR framework.”

Brian Chavez created the C# RethinkDB.Driver client library so he could use Mono to run .Net web applications on Ubuntu, but he’s enthusiastic about .Net Core as an official cross-platform .Net experience.

The open source nature of .Net is important to many businesses too, says Hunter. “I've heard companies say they run an 80-20 model where they use 80 percent open source as part of their DNA.” That helped drive Microsoft’s decision to open source the entire .Net platform. “I never want to sit down with a customer who says I chose someone else over you because they’re more open.”

Opening .Net up for community contributions has helped bring it to a wider range of platforms than Microsoft could ever have done on its own, including FreeBSD. And AWS quickly created an SDK for .Net. “Being cross-platform gives legitimacy to the platform,” Hunter says. “You’re not isolated to a Microsoft world. We don’t hamstring the Linux version; we make sure the performance is in the same ballpark as on Windows.”

This story, "What should you do with your .Net apps?" was originally published by CIO.

Copyright © 2016 IDG Communications, Inc.

How to choose a low-code development platform