A .Net Core app (soon 2.1) with Xilium.CefGlue (.Net bindings for Chromium) sub-processes can be converted using Desktop Bridge for the Windows Store?
I am developing .net applications on a mac using parallels where I have a windows VM and all my .net tooling.
now that visual studio 2017 can run on mac, would i be able to eliminate my method and run visual studio direct on my mac and seamlessly be able to move my code over to the mac version and compile and develop asp.net web applications?
I am only worried about web applications.
I am very new to asp.net core 1.0. I want my services to built on windows platform and host/run on linux or mac. What are the possible ways to do the same ?
I'm having a i.mx35 board on which the windows CE 6.0 present. need to know
will it run or debug the Qt application? or should i port the embedded Linux on the board for development, cause Qt does not support windows CE directly and i don't have any SDK to develop app for it.
will it support instrument cluster type graphics, created in Qt Quick (which having qml Flies)?
any idea on this.
I read that WinRT does not have a layer that support .NET applications here: seek to 1:55 seconds http://www.youtube.com/watch?v=TI0ABjSKAGU
I also read that .NET 4.5 framework provided support for Windows Runtime here Differences between .NET 4.0 and .NET 4.5 in High level in .NET.
Here is my confusion:
Does that mean that I can run my .NET application on Windows Runtime now? How WinRT supports my .NET app? I have an idea that .NET can only be used to create web applications which are usually consumed using webbrowsers. If WinRT had a browser then why WinRT had problems in running my .NET application?
WinRT is an OS/layer which is installed on ARM based machines and tablets (Surface tablet).
I want to know what type of .NET application I will be developing for WinRT given that I now have support for Windows Runtime in .NET 4.5 framework.
If you are developing an application for the Windows Store, you will be developing it using the Windows Runtime (WinRT). That is the only option today. After you've made that choice, you can choose between a C#/XAML or a HTML/WinJS user interface. You don't "choose" .NET 4.5. You're selecting the Windows Runtime.
There are two distinct platforms, and overlapping terminology:
Windows Runtime (usually abbreviated as WinRT) and .NET
The .NET platform has existed and been available for production development purposes since the release of Visual Studio 2002 and .NET 1.0. Using this platform, and its modern versions (4.5.1 with Visual Studio 2013), you can build what would be considered a traditional Windows executable or application. From Windows Services, desktop applications written for several different UI platforms (WinForms and WPF), and sophisticated web applications all can be created and are portable across all modern versions of Windows, with the exception of WindowsRT. WindowsRT runs traditionally on lower powered ARM processors, and cannot execute a traditional application written for .NET.
Unfortunately, the names and capabilities are very confusing. WinRT (Windows Runtime), which is the platform, can be used to create Windows Store applications. It cannot be used currently to build what would be considered a native desktop application. .NET 4.5 cannot be used to build a Windows Store application. The WinRT platform can target any modern Windows device, from tablet, to desktop. WinRT also runs on Windows RT, which are the lower powered, non-x86 chipsets like ARM.
All platforms share several languages: C#, VB, and C++.
The WinRT's libraries manifest as a layer that look identical to nearly identical in many cases to .NET libraries. In fact, the documentation can often be used for either in common cases. More confusingly, it's sometimes referred to as .NET for Windows Store apps. You'll see how it's not a complete .NET 4.5 implementation.
The confusion often comes from the fact that they are so similar. The underlying code for WinRT is not .NET. It is opaque (and mostly written in C++). It looks like .NET 4.5, and often performs/behaves like .NET 4.5, but it isn't the same platform as is used by a traditional .NET 4.5 application. While you can create code that can run as a portable class library and use functionality and APIs that are common to all platforms (.NET and WinRT), a WinRT application can not directly call .NET 4.5 code.
The Windows Runtime is a highly sandboxed and API-curated developer experience, much like is available on various phone platforms, like the Windows Phone Runtime, iOS, and Android. If you look at the "surface" area of the .NET platform and CLR, you'll see how large and complex it has become, and that there are a lot of capabilities that either don't make sense in the context of a Windows Store application, or simply aren't safe. I expect over several releases Microsoft will include additional features to the Windows Runtime from the core Windows OS. Those APIs may/may not mirror similar functionality found in .NET 4.5.
However, on a Windows 8+ system, a Windows .NET application can access a subset of the APIs available in the WinRT (the marketing folks at Microsoft refer to it as a "streamlined" set of APIs). For example, you cannot access the WinRT UI platform and create a desktop application that builds its interface using WinJS or XAML, which are only available in a WinRT application.
.NET Framework Support for Windows Store Apps and Windows Runtime