A cool preview of things to come in C# 8: [WayBack] Build 2018: The Future of C#
Via: [WayBack] C# 8 changes, exemplified #csharp – Lars Fosdal – Google+
–jeroen
Posted by jpluimers on 2018/06/13
A cool preview of things to come in C# 8: [WayBack] Build 2018: The Future of C#
Via: [WayBack] C# 8 changes, exemplified #csharp – Lars Fosdal – Google+
–jeroen
Posted in .NET, C#, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/06/01
Interesting [Archive.is] Thread by @shanselman: “Sure. Not too complex. Thread -> .NET is a family. * Core runs on containers, many Linuxes, Windows and Mac. OSS, moves fast. * Framework […]”
It answers [Archive.is] Thread by @domenic: “Having been out of the scene for over 5 years now, I’m extraordinarily confused by what’s going on over in .NET land. Not only the “what”, b […]”
Dominic was confused by .NET Core going to support Windows desktop UI apps as platform specific packages to a a cross platform foundation as announced in [WayBack] .NET Core 3 and Support for Windows Desktop Applications | .NET Blog
Via: [WayBack] Miguel de Icaza on Twitter: “Good thread on the evolution of modern .NET by @shanselman… “
–jeroen
Posted in .NET, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/05/31
Very interesting read: “Garbage Collection Design” by Maoni Stephens at [WayBack] coreclr/garbage-collection.md at master · dotnet/coreclr.
It’s part of this series of documents:
The Book of the Runtime
Welcome to the Book of the Runtime (BOTR) for the .NET Runtime. This contains a collection of articles about the non-trivial internals of the .NET Runtime. Its intended audience are people actually modifying the code or simply wishing to have a deep understanding of the runtime. Below is a table of contents.
at [WayBack] coreclr/Documentation/botr at master · dotnet/coreclr
I got there via these links:
–jeroen
Posted in .NET, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/05/30
The thread at [WayBack]: Allow for floating windows · Issue #10121 · Microsoft/vscode · GitHub made me discover a few things, which I have commented there.
Reminder to self: find the Windows keyboard shortcuts as well.
Thanks @steinhh for the
Cmd–KOkeyboard combination. I was not aware of that yet and I am going to use this next week on a multi-monitor system to see how well that works.Your tip made me found the PDFs below and made me make the lists/screenshots below as well.
Terrific! Thank you, thank you!
- https://code.visualstudio.com/docs/getstarted/keybindings,
- https://code.visualstudio.com/shortcuts/keyboard-shortcuts-macos.pdf and
- https://code.visualstudio.com/shortcuts/keyboard-shortcuts-windows.pdf
The bindings (on Mac) I found with their screenshots:
Cmd–Shift–P: show all commands
Cmd–KO: open current file in new WindowCmd–Shift–N: open a new window
Cmd–KCmd–R: open keyboard shortcuts reference PDF for current OS in the default web-browserCmd–KCmd–S: open keyboard shortcuts editor
The keyboard shortcuts editor has a search which can find bindings on the keybinding name itself or the command name:
–jeroen
Posted in Development, Software Development, Visual Studio and tools, vscode Visual Studio Code | Leave a Comment »
Posted by jpluimers on 2018/05/10
It’s a great too, so I need to invest more time into using MemoScope.Net – Dump and analyze .Net applications memory ( a gui for WinDbg and ClrMd )
Way too manny features to describe here, so get that at the GitHub repository below.
Source: [Archive.is/WayBack] fremag/MemoScope.Net: Dump and analyze .Net applications memory ( a gui for WinDbg and ClrMd )
Via Matthijs ter Woord.
–jeroen
Posted in .NET, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/05/10
Hopefully by now the ToC has gotten bigger at [WayBack] Multi-threading in C#: Back to Basics (Part 1 of N) – CodeProject.
At the time of writing it was this:
–jeroen
Posted in .NET, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/04/27
HEAD – A list of everything that could go in the of your document
Wow. head is like a page by itself.
Source [WayBack] joshbuchea/HEAD: A list of everything that could go in the of your document
Via: [WayBack] HEAD – A list of everything that could go in the of your document https://github.com/joshbuchea/HEAD – This is why I Code – Google+
–jeroen
Posted in .NET, Development, HTML, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2018/04/25
For my research list:
–jeroen
Posted in .NET, Delphi, Development, Software Development | 4 Comments »
Posted by jpluimers on 2018/04/16
Because the CLR is a managed environment there are several components within the runtime that need to be initialised before any of your code can be executed. This post will take a look at the EE (Execution Engine) start-up routine and examine the initialisation process in detail.
Lots of interesting stuff happening before your code even gets executed. Many of the pieces can log.
Source: [WayBack] The 68 things the CLR does before executing a single line of your code (*) · Performance is a Feature!
Via: [WayBack] Good stuff to know! – Ondrej Kelle – Google+
–jeroen
Posted in .NET, C#, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2018/04/04
Shamelessly adapted from [WayBack] C# 8.0 features Extension everything — a new syntax for extension methods that will also allow extension “other things,” like the much-anticipated exte… – Lars Fosdal – Google+, including the original posts where the topics were covered:
C# 8.0 features
Post 1
[WayBack] C# 8.0 Features: A Glimpse of the Future – NDepend: C# 8.0 is on the horizon and will be here before you know it, bringing with it some interesting functionality. Let’s take a peek into the future.
Extension everything — a new syntax for extension methods that will also allow extension “other things,” like the much-anticipated extension properties.
Default implementations on interfaces — this allows you to implement methods on interfaces, giving them a default implementation. That will enable you to add new methods to interfaces without breaking its clients.
Nullable reference types — probably one of the most anticipated features ever. It’s a reinterpretation (a “retcon” for you comic book geeks out there) of all the reference types as nullable and the introduction of a new syntax to denote nullable types, accompanied by several types of static checks, to prevent several classes of errors regarding these types. Say farewell to the null reference exception!
Post 2
[WayBack] C# 8.0 Features: Another Glimpse of the Future – NDepend This post covers two probable C# 8.0 features: null coalescing assignment and records. It explains what they are and reports on their current statuses, as well.
Null coalescing assignment — a very simple feature to shorten the check for null before assigning to a variable.
Records — this one is pretty interesting. It’s basically a very short way for you to declare classes that are only data holders. The compiler gives you Equals and GetHashCode implementations, a constructor, properties, and immutability for free, allowing you to do something more interesting with your life than writing loads of boilerplate code.
Post 3
[WayBack] C# 8.0 Features: A Final Glimpse Of The Future – NDepend: Here’s our final post in our C# 8.0 series, where we glimpse into the future. Today we’ll cover another two possible features: target-typed new expressions and covariant return types.
Target-typed “new” expressions — a way for you to omit the type from a constructor call, making the code simpler and less redundant.
Covariant return types — a much-anticipated feature that allows an overriding method to return a more derived type than the original type from the base class.
I really hope they publish the full specs soon, but given that the C# 7 specs yet have to (see [WayBack] C Sharp (programming language) – Wikipedia: Versions), I do not hold my breath, even though it had lots of interesting new stuff too:
–jeroen
Posted in .NET, C#, C# 7, C# 8, Development, Software Development | Leave a Comment »