Linked by Thom Holwerda on Fri 6th Sep 2013 15:22 UTC

The new apps look and behave much like the native apps you find on Windows and OS X. They're built using web technologies, but also with Chrome-specific code that means they won't be able to run on other web browsers - they're truly Chrome apps. They can exist outside of your browser window as distinct apps, work offline, and sync across devices and operating systems. They can also access your computer's GPU, storage, camera, ports, and Bluetooth connection. Chrome Apps are, for now, only available through Chrome on Windows or Chrome OS on a Chromebook. Mac users will have to wait another six weeks before their version of Chrome will be updated.

This is very important for Chrome OS - since this means it can now have applications outside of the browser. Google's plans for Chrome OS suddenly became a whole lot clearer.

Thread beginning with comment 571539
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by BluenoseJake
by Nelson on Fri 6th Sep 2013 22:45 UTC in reply to "RE[3]: Comment by BluenoseJake"
Member since:

Windows shipped with versions of .NET bundled. Every version of .NET installed after that runs side by side.

Reply Parent Score: 3

moondevil Member since:

Every version of .NET installed after that runs side by side.

Go tell that to everyone that needs to target 4.0 and 4.5,thanks to the stupid idea of an in-place replacement.

Edited 2013-09-07 08:21 UTC

Reply Parent Score: 2

Nelson Member since:

You have to target 3.5, 4.0 and 4.5 as well. Microsoft has tested that the .NET4.5 CLR (sans the new libraries) is behaviorally equivalent to the .NET4 CLR.

There's a lot of work done around the tooling to help with the corner cases (.NET 4.5 projects being referenced from .NET4 code) and VS is smart enough to create a manifest that will automatically prompt you at runtime that you require .NET4.5

The thing that's been different now (with 4.5) from previous (2.0 -> 3.0 -> 3.5) is that the CLR2 was completely unchanged across those releases. Only work on top of them (WPF, WCF, WF, etc.)

With .NET 4.5 the actual CLR has changed (perf improvements and deep architectural changes for WinRT iirc).

Honestly, I'm glad they're moving towards out of band NuGet releases rather than throwing everything in .NET, the versioning issues aside.

Reply Parent Score: 3

BluenoseJake Member since:

I said new versions. Not versions that existed when that particular versions of Windows came out. Windows 7 does not automatically get .net version 4, for example, it is an optional download in Windows Update.

Reply Parent Score: 2

Bill Shooter of Bul Member since:

Not until windows Vista in 2006. We were following the development of Windows XP and .Net, hoping that both would end up getting shipped together. It didn't happen with the initial release or any of the service packs.

Reply Parent Score: 2