Reimagining APP Development with the Windows Runtime

The Windows Runtime enables Language Choice

The Windows Runtime is Natural and familiar

[DllImport("avicap32.dll", EntryPoint = "capCreateCaptureWindow")]static extern int capCreateCaptureWindow(  string lpszWindowName, int dwStyle,  int X, int Y, int nWidth, int nHeight,  System.IntPtr hwndParent, int nID);[DllImport("avicap32.dll")]static extern bool capGetDriverDescription(  int wDriverIndex,  [MarshalAs(UnmanagedType.LPTStr)] ref string lpszName,  int cbName,  [MarshalAs(UnmanagedType.LPTStr)] ref string lpszVer,  int cbVer);

using Windows.Media.Capture;MediaCapture captureMgr = new MediaCapture();await captureMgr.InitializeAsync();// Start capture preview; capturePreview// is a CaptureElement defined in XAMLcapturePreview.Source = captureMgr;await captureMgr.StartPreviewAsync();

The Windows Runtime is a Rich in functionality

The Windows Runtime is Fast and Fluid (Native and Async)

The Windows Runtime enables Hybrid Apps

Frequently asked Questions

Q. Is the Windows Runtime a replacement for the CLR or the Microsoft. NET Framework?

A. No. The Windows Runtime does not replace the. NET Framework or any other frameworks. When you build a Windows Store app in C #, your code is still executing using the CLR. Not only so, but a subset of the. NET Framework (AS-well as Win32 and COM) are available for you and if building you R Windows Store Apps.

Q. Why writing Windows Store apps in C + +, I ' m using C + +/CLI?

A. No. The Code using the Windows Runtime for Windows Store Apps is written using C++/CX. Though it is truly native. C + +/CLI at first. You won ' t introduce garbage collection or other C + +/CLI features into your native app.

Original address