I eagerly awaits more: Stephen Cleary (the blog): A Tour of Task, Part 0: Overview (“awaits” is a play on words).
At least! But only a preview for now.
Why does C# use UTF-16 for strings?
In fact, it doesn’t use real UTF-16 because “C# uses UTF-16 in 2014 because Visual Basic used UCS-2 in 1993” despite “UTF-16 was not invented until 1996”. It use UTF-16 as if surrogate pairs doesn’t exist…
Lots of helper extensions to format BCL types to more readable strings (and reverse).
Just like any other library, I have concrete cases of use of some extensions and some others seems useless. I dream of possibility to choose which subsetI take from a nuget library. Splitting in multiple parts is boring to use. This must be mitigated by the fact that binary is small: 76 Ko plus localisations assemblies.
Humanizer includes an evolution of the excellent ByteSize.
Detailed samples on the now (since Windows 8.1 Update) possible communication between Windows Store client connected to a local server hosted in local Desktop application.
It only works for side loaded applications. If you don’t know everything about this kind of app, all you need to know is available on technet here.
EDIT: This is now simplified by project templates: Brokered WinRT component project templates now available.
EDIT: And now how to distribute C++ Runtime for Sideloaded Windows 8.1 apps (when C++ runtime cannot be provided by Windows 8 Store).
Permits to nest/unest files in project. It’s convenient to gather partials class without always creating folders.
A very good description of what is serialisation of a XamlWriter and how to interfer with this mechanism Being written by XamlWriter – Data See, Data Do – Site Home – MSDN Blogs.
“Atom is a specialized variant of Chromium designed to be a text editor rather than a web browser. Every Atom window is essentially a locally-rendered web page.