Is Universal Windows Platform the replacement of WinRT of Windows 8 and Windows Phone apps?
I mean, there was a WinRT platform to develop metro apps exclusively for Windows 8. Now, that is replaced by UWP, isn't it?
That is correct, UWP is the new platform for ALL Windows devices going forward (Win 10+). However WinRT is not replaced by UWP but is instead an extension on top of it, making UWP a much broader set of APIs that can be used across even more devices. As Microsoft themselves state:
With this evolution, apps that target the UWP can call not only the WinRT APIs that are common to all devices, but also APIs (including Win32 and .NET APIs) that are specific to the device family the app is running on.
The UWP platform supports the "Universal Device Family" class of APIs which is then supported on ALL windows platforms (Xbox, Phone, Desktop etc). There are some extension families that you can use that will limit the apps reach, such as a "Mobile Device Family".
These specific device family APIs can however be checked for and used at runtime gracefully. For example you could show your own position using GPS on a phone, but not enable that functionality on a Xbox.
I hope this answer helps you, if you have any more questions about this I recommend reading this article about the UWP platform:
Source: https://msdn.microsoft.com/library/windows/apps/dn894631.aspx
Have a wonderful day!
This is a bit confusing because in Windows 8.x, "Windows Runtime" was actually used to refer to a few different things:
A new pattern (and supporting code/OS components) for defining and consuming Windows APIs, meant to largely supersede "Win32" (i.e., flat C-style) and classic COM for new APIs in most scenarios. This was/is really about language interop: allowing the Windows team (and potentially others) to create components in C++ that expose APIs that don't depend on GC or a runtime like the CLR, but still feel relatively natural to use from C# or JavaScript without needing manually written wrappers.
The set of Windows APIs that follow the above pattern.
A new platform/environment for building and running a new type of Windows app, which are meant to have some of the characteristics of mobile and web apps in terms of causing fewer potential problems with system security, reliability, performance, battery life, etc. This is what evolved into UWP with Windows 10.
In the Windows 8 days, these apps were called "Metro style apps" during most of 8.0's public preview period, and officially dubbed "Windows Store apps" just before RTM. The platform/environment for these apps ... officially didn't really have a name (other than "platform for Metro style apps"). Unofficially, people (including at Microsoft) sometimes referred to it as "Metro" (a whole can of worms in itself) or ... "WinRT".
So what's the relationship between WinRT "proper" (definitions 1 and 2), and unofficial WinRT definition (3) aka UWP aka the formerly-nameless "platform for Metro style apps"? Well, since WinRT and the new app platform were both introduced in Windows 8, most of the WinRT APIs at that time were specific to the new platform. The app platform (and Store policy) at the time was also much more restrictive about which legacy Win32 APIs were allowed for use in apps - for the most part this was less about any technical limitation and more about the team hoping to use the new apps as an excuse to clean up the bloated Win32 API surface. But technically, WinRT is meant to be the common pattern for new Windows APIs in general, whether used in UWAs or not, and "UWA vs. classic app" and "WinRT vs. Win32" are mostly independent; over time, they've gradually enabled more WinRT APIs for use outside UWAs and also relaxed their policies on using a lot of legacy Win32 APIs in apps (and also continued to introduce new flat C-style APIs for certain use cases).
So to summarize, it's not technically accurate to say that "UWP replaced WinRT", though understandable since this stuff is pretty confusing. UWP replaced the nameless app platform (3); essentially it's just an updated version that's been ported to other device types and integrated with the classic desktop UI. WinRT, in its proper definition (1), continues to be the basis for new Windows APIs for use in UWAs and even outside them.
Windows Universal Platform is the development platform going forward for devices running Windows. Previously, development was separate for Desktops and Tablets vs Phones. With UWP you are now able to target any device running Windows 10, could be phone, desktop, tablet, xbox. The beauty is that you can now use one Binary for all of these platforms and has brought us much closer to a truly to a universal Windows app.
So, to answer your question, yes, UWP is the platform going forward for any device which runs Windows 10
I am new for SAP Mobile Platform (SMP 3.0).
As per my basic research, I came to know that 'Agentry Toolkit' is one of the component of SMP 3.0 SDK. I installed SMP 3.0 SDK.
Can anyone help me to describe what is actually 'Agentry Toolkit' & How to use it in app (Hello World App) ?.
Thanks in advance.
The key thing to remember is that SAP Mobile Platform (SMP) is a server which hosts and manages a variety of mobile application types. The mobile platform has to support a number of 'legacy' technologies e.g. Sybase mobile business objects etc.
SAP acquired a company called Syclo (it has a number of products the most common one is called Work Manager).
The SDK is a set of tools that developers mainly use to develop and deploy mobile applications. It contains a number of SDKs so that developers can integrate with the various mobile "components" that run on the mobile platform.
The Agentry Toolkit is a plugin to Eclipse which allows you to create, edit and modify Agentry applications.
You can of course create an application from scratch and build a "hello world" using this.
We are developing a lightswitch app that will have a silverlight plug in controller that will allow for handwriting recognition and translation. we want to use this exclusively on a win8 tablet. we know that it has to be used on the desktop side of the tablet. We also know that the win8rt side has access to different tools that allow of handwriting recognition. (InkManager class) - is there any way to get access to these necessary classes from the desktop side of the win8 tablet.
This post by Scott Hanselman might help you.
Quote:
I was trying to access some of the sensors that are built into this
Intel Ultrabook that runs Windows 8. However, while there's support
for Location Sensors built into the .NET 4 libraries on Windows 7 and
up, I want to access the complete Sensor and Location Platform that is
built into Windows 8 itself. Those APIs are available via COM and I
could call them via COM, but calling them via the WinRT layer is so
much nicer. Plus, this is kind of why WinRT exists.
There's also an example using VB.NET on TheCodeProject
I'm developing mobile application in j2me. My target phone is "Nokia". In my app I'm using some Nokia API's .Now the requirements change, so that many other target devices than Nokia are also included. Here my doubt is if, on other phones, the mobile app developed with Nokia API is working or not. Please share your ideas.
It wont work, you might get ClassNotFoundException after running the midlet on different devices. Nokia UI library will residing be in Nokia mobile OS.
I haven't tried but if you can add the Nokia UI jar in your project as library and then try it on other devices. I will also try it. But i guess some of the api's will be having hardware dependency like sound etc..
I know this is repeated question. I read almost all the threads , googled a lot and became more confused. I read Microsoft Mobile Internet Toolkit (MMIT) is not used anymore and Windows Mobile 6.5 Developer Tool Kit is widely used .
Requirement:Develope and publish websites for mobile phones.
Envoirnment:VS2008/.net 3.5
I am new to mobile web application development. I want to know how to start ,what are the frameworks i should know/download,sample websites or articles..
Thanks,
Vanitha
If you want to create web applications for mobile devices using microsoft technologies check out this site:
http://www.asp.net/mobile
It has simple how-to.....
If you're going to invest in a new skill, I'd focus on iPhone and Android development - they're far more widespread than windows mobile.