UWP? UWP !, Uwp

UWP? UWP !, Uwp
UWP? UWP! -What about Build 2015?

Build 2015 ended successfully. I wonder how many of you watched the live video during the night? In any case, you may be curious about what amazing news Microsoft has published at this Microsoft developer feast. I have sorted out some UWP-related content, but it is not comprehensive. I hope readers can correct me more.

(The images involved in this article are all from Build)

1. UAP rename UWP

The Application name in Win10 is officially determined as the Universal Windows App. It may be to clarify the relationship with the previous UAP to indicate that it has actually achieved the "Universal ". Yes, UWP is one of the most important topics of this Build Conference. Its cross-platform compatibility, multi-language support, and support for other platform applications all have an unprecedented "Universal ". Microsoft has changed and become more open and wider, which should make a lot of developers clapping.
This message is just an introduction. Details about UWP are described below.

2. Large and different App Store

WP/WinRT users may think that there are too few applications in Windows App Store, right? Microsoft seems to have noticed this. In the Win10 App Store, Microsoft will "add users in the app store by no means" to ensure that UWP has a thriving ecosystem. Let's take a look at something:

Comprehensive and common equipment developed by Microsoft

Windows 10 does not have WP10. From PC to RT, from Lumia to Surface, from IoT development board carrying the system to Xbox with powerful computing power, the same Windows 10 is used, the difference is only the resolution and peripherals. Presumably, Windows will be completely flushed in high-resolution screens.
More relevant to this topic, all devices using Windows 10 as OS will share the same AppStore. At the same time, Microsoft provides a complete set of tools for App designers to adapt their applications to various platforms. Presumably, this is enough for WP users to feel excited.

Microsoft's mandatory killer: adding traditional Win32PE programs

The traditional win32pe, which is also widely used by everyone, is the largest executable file in the desktop environment that msdos has ever attacked. Converting it to UWP seems a little sci-fi, but Microsoft is actually putting it into practice.
Speaking of this, we have to talk about the Project centenrix mentioned in this Build conference-although the Project is still in the development stage, we cannot directly enjoy its results, but we can expect that, once the project is put into practical use, it will bring a revolutionary change to the UWP application ecosystem: the data given in Build shows that more than 17 million of mature Traditional PE applications exist, this is not a small Helper Program. The impact of transforming them into UWP is self-evident. It is Microsoft's secret.

Haina baichuan-Android and iOS applications can also run

It is a sci-fi setting, but it also seems to come true step by step: Project ASTORIA provides plug-ins embedded in Eclipse/Android Studio to help Android projects generate UWP that can run on Windows 10, microsoft claims that it has a high code reuse rate and can generate UWP based on the existing Android logic. In addition, iOS applications can migrate to UWP through similar means, but the details are still under development.

3. A developer-friendly integrated development environment

Speaking of the application ecosystem, developers are of course an essential part. If they cannot please developers, who will write UWP? (Cough )... To put it bluntly, Visual Studio 2015, as the leading IDE of Microsoft, will also undergo great changes to bring a better development experience to UWP developers.

Native support of Github

I don't know how many developers who use VS to develop applications use Team Foundation Server? In all fairness, this is a very good source code hosting tool, but we should be familiar with all major source code hosting tools in the open source field, such as git/svn. To show its sincerity in embracing open source, Microsoft said it would add native support for github in VS2015.

Awesome ~

Cross-platform

Ha, VS should also be cross-platform? Yes. In this Build, Microsoft announced the release of Visual Studio for Linux and Mac OSX. In the future, even unix programmers can use vs, but they do not know whether other versions of vs will carry. net runtime. If so, it is possible that the development of UWP on non-Windows will come true soon.

UWP development tool upgrade

In the new VS, a series of auxiliary tools will be added to help develop UWP, such as the more comprehensive Design view, better and more detailed debugging tools for analyzing software running performance and resource conditions, as well as Live Visual Tree Inspector that allows you to view UI element la s in real time during debugging (similar to browser functions). Their existence is undoubtedly another gospel of UWP developers.

Adding Node. js and python

As the vane of the scripting language, Node and python are undoubtedly the most talked about by developers, and I am also a loyal fan of Node. Previously, VS was amazed to add Html + js to UAP development tools. Now Microsoft will fully support Node. js and python development and provide related tools in VS2015. Although it is not clear whether they can be used for UWP development, from the trend of this behavior, it is not long before to use scripting language to write related components for UWP.

 

To be continued, the next blog will detail the new features of this Build for UWP developers.