Windows RT .NET compatibility - windows

I just need to know if I need the same framework to develop an app for Windows 8 for Tablets (Windows RT) and PCs or the tablet one still uses .NET compact framework.

The only type of applications that run on Windows RT (ie. the Tablet/ARM version of Windows 8) are Windows Store Apps. These are full-screen applications that run on top of the WinRT API.
You can use a subset of .NET 4.5 on these devices, and use XAML to build your interface just like you would with WPF on the desktop.
You can read more on MSDN - .NET for Windows Store apps overview. This article describes a lot of the changes between the main version of .NET and the Windows RT subset that's available to you. Generally, Windows.Runtime will provide alternatives to some of the .NET methods that no longer exist.

http://www.infragistics.com/community/blogs/nick-landry/archive/2012/06/19/developing-apps-for-microsoft-surface-windows-8-windows-rt-and-windows-phone.aspx
here are all the info about that

As for the .Net compatibility, the .NET for Windows Store apps link states that the a lighter version of the .Net Framework (aptly called ".NET for Windows Store apps") will be available in Windows RT and so the available APIs too will be a subset of those available in the Full Desktop Version of the Framework. Eg. In Windows RT, Windows Forms will not be availble.
You can also create a Portable Class Library project to develop a .NET Framework library that can be used from a Windows Store app. The project must include .NET for Windows Store apps as one of the target platforms. This is useful when you want to build functionality that can be used from apps for different platforms, like Windows Phone app, desktop app, and Windows Store app.
Dev Center - Windows Store apps is the best (and official) place to get started.

Related

Can Universal Windows Platform be used to develop windows software and not app

I wished to develop a specialized software and NOT an app, which will be deployed at a few customer sites ultimately and not to be posted on Microsoft Store. Can I use Universal Windows Platform for it? I did some research and the official documentation of Microsoft says -
The Universal Windows Platform (UWP) is the app platform for Windows 10. You can develop apps for UWP with just one API set, one app package, and one store to reach all Windows 10 devices – PC, tablet, phone, Xbox, HoloLens, Surface Hub and more.
We want to develop a specialized software, with all its installers / DLLs / binaries etc etc which we will ship to a few customers and install at their PCs. So, my question is - Can we use Universal Windows Platform for developing such a software? Or if it be used only for app development, which ultimately needs to be loaded on the Microsoft Store for disbursement?
UWP apps do not have to be distributed via public Microsoft Store. You can distribute the apps via sideloading and alternatively via Microsoft Store for Business which is a company-specific view into Microsoft Store, where you can publish internal apps.
Furthermore, you can package existing Desktop apps as UWP apps including their installers with the Desktop Bridge, which is useful when your app includes functionality, which is unavailable in pure UWP apps.
The main advantage of using UWP especially in conjunction with Microsoft Store for Business is simpler deployment and easier install and update lifecycle, however it might not suit you in complex scenarios.
2 ways to go about this (of a couple more)
1. You can distribute the appx as you would an exe and have the client use side loading to install it on whatever machine is needed.
2. you can release it in the Microsoft Store for Business or Microsoft Store for Education

windows core iot dll

I want to controll a robot arm with a raspberry pi running windows 10 iot. There is a dll to controll the arm. In the documentation of the dll it says that a .NET 2.0 framework is required. Is it possible to use the dll in my application for the windows core iot?
For Windows 10 IoT Core you create apps to do such things using the Universal Windows Platform (UWP) framework. This uses .Net Core. Not the full framework.
Check the latest version of the assemblies you require.
https://www.microsoft.com/net/core

What type of component should be used to write SDK to support on windows 8.1 and windows universal devices

I have a requirement to develop a SDK(kind of class library) for Windows app supporting Windows 8.1 and Windows universal apps. Please suggest me the right type to choose for this.
At first I was thinking to use Portable class library supporting these 2 platforms but later on some researching found out Windows Runtime component(Universal apps) and read that using this would support app build using non managed code too(C++, JavaScript) which kind of seemed good for me. but when I try to refer this into a windows 8.1 app it says not supported, Do I need to build a separate windows runtime component again for this(I see Windows runtime component(portable for universal windows 8.1 template)?
Is there any chance I could build this without the need of having 2 projects for different platforms?
I've been able to successfully use a WinRT component targeting Windows 8.1 in a Windows 10 app before, but it might have changed and YMMV. Try it out.

Convert windows phone application to universal one

Recently Microsoft announced ability to create universal applications in Visual Studio 2013. Is there any easy way to convert existing Windows Phone 8 application into universal or i have to create new project and properly move the code manually?
It is not about converting a project type or moving code. You will have to port your app from one runtime to another. This is because the Universal project templates use the Windows Runtime APIs where as your existing Windows Phone 8 application uses the Silverlight APIs.
Windows Phone Store apps use the same app model and UI framework as Windows Store apps do, and they use the Windows versions of common features such as background tasks. You will still be able to reuse a lot of your existing code, but these differences mean that it really is a porting exercise, more than just an update, to move a Windows Phone 8 to the new app model.
(Source)
There are some features that are available in Windows Phone 8 for which there is no Windows Phone Store (Universal apps) equivalent. See more here.
The right-menu option is "Add Windows 8.1...". That will add Windows 8.1 support and add a Shared section to both projects so you can share code between then.
In your solution, right click your Windows Phone application and select "Add Windows 8.1..." and follow the prompts.

Porting Windows Phone7 application to Windows 8

I ported my windows phone7 application to windows 8(just copy paste the xaml and c# code in visual studio 2012->new->project->WPFApplication) and made changes in UI sizes.The problem is the .exe file(after building wpf application) runs only in the system with .NET framework installed.I want to run my application in all system running windows(7(32/64),xp,vista).I am newbie to windows application basically wp7 developer.Thank u.
If you really want to port a windos phone 7 app to windows 8, You should go through the following resources. They provide most of the information.
http://msdn.microsoft.com/en-us/library/windows/apps/hh465136.aspx
http://leventoz.wordpress.com/2012/03/07/moving-a-windows-phone-app-to-windows-8-a-case-study-part-1/
http://leventoz.wordpress.com/2012/03/11/moving-a-windows-phone-app-to-windows-8-a-case-study-part-2/
WPF is a part of the .NET framework, so you can't write a WPF application that can run without the framework on the machine.
If you want to create a binary that run on the classic windows runtime you can't use WPF/C#/VB etc.
Best thing if you want to port your Windows Phone app to Windows 8 is to create a Microsoft Store app, File > New Project > Blank App in VS2012. The app won't run on anything except Windows 8 but the Microsoft Store for Windows 8 is probably the best place to have your app if it's ported from Windows Phone.
Migrating application to WP7 is not that easy as it sounds. There is lot of different APIs and also limited async/await in WP7 when using this extension.
I would probably recommend starting with this MSDN article. It describes basic problems and challenges and also contains useful namespace and API mapping:
Migrate/port a Windows Phone 7 app to a Windows Store app

Resources