How to use the Microsoft technology stack

The recent changes in the Microsoft technology stack have led developers and leaders to wonder what technologies they should be focusing on. Microsoft itself does not want to object to technologies such as Silverlight at the official level, and they prefer to let the technology fade out of sight, or the situation could be even more confusing. If you want to know the answer to the question, you can see ". NET Business Application Technology Guide "This small, prestigious document. The document, published earlier last year, delves into the areas in which Microsoft intends to work and what technologies we should avoid.

The following diagram is a good starting point for us to explore Microsoft and its related technologies.

Try to give up Silverlight and Flash as soon as possible

While the old. NET technologies of WinForms and Web Forms still occupy a place, the RIA containers such as Silverlight and Flash are definitely out. As shown in Figure 5-15 below, Microsoft does not want to wait for the 10-year lifecycle that Silverlight 5 plans. They are already planning to give up RIA containers by the end of 2015.

High-end applications are more likely to use local technology entirely, while low-end applications expect HTML5 capabilities to continue to evolve. Although developers are not pushed to a specific technology, the things we have to be aware of about this shift are:

If you are transitioning to a local application, you can xaml/that can be run on any Windows device by birth. NET as a goal so you can take advantage of your existing skills and even code. The Portable class library also allows you to share class libraries, including Silverlight, across different platforms.

For browser-based HTML5 applications, Microsoft provides the main tools and frameworks that help you create applications that can be used on any device based on the latest standards. Silverlight and HTML interoperability also allow you to make a gradual transition through a hybrid application.

Move

The Windows 8 store has three equal but different options

Microsoft used to be reluctant to push developers to a specific technology stack for Windows 8 store applications. This policy has not changed now; The primary criterion for choosing between these technologies, NET/XAML, C + +, and JAVASCRIPT/HTML5, is which technology developers are most familiar with.

In addition, they mention C + +, because it has a performance advantage. Reusability is not a point of concern because these three platforms share code and resources between Windows Phone and Windows desktop.

Local options for Windows Phone

The technology recommended by Windows phone is. NET and C + +. Again, you need to be aware of the performance benefits of C + +, but the most they say is that developers should use technologies that are more familiar to them.

Although Windows Phone is compatible with Phonegap/apache Cordova, this is not mentioned. The reason for this may be that they think the performance of phonegap on small devices is worse than. NET or C + +. Performance is no doubt the most important topic at the 2013 build convention, beyond other topics such as General usability, visual design, and deep OS integration.