InfoQ Homepage .NET Languages Content on InfoQ
-
.NET Core 2 Brings Visual Basic to Linux and macOS
Microsoft has moved closer towards bringing Visual Basic into place as a first-class citizen on the .NET Core platform. As part of the .NET Core 2 release, VB developers can now write code that targets .NET Standard 2.0, increasing the deployment platforms available. Importantly, this means the same executable or library that runs on Windows can work on macOS and Linux.
-
Microsoft Reiterates its Support of F#
Mads Torgersen and Philip Carter, respectively C# and F# program managers at Microsoft, published a post promoting the use of F#. The post is a follow-up to a presentation on F# at Build 2017. They talked about how Microsoft wants to remove obstacles to F# adoption and the F# improvements Visual Studio 2017 brings.
-
C# 7.2 and 8.0 Roadmap
Features are already being lined up for C# 7.2 and 8.0 including nullable reference types and limited multiple inheritance.
-
An Early Look at C# 7.1: Part 2
Yesterday we looked at Async Main and Default Expressions. Our tour of C# 7.1 continues with the proposals titled Infer Tuple Names and Pattern-matching with Generics.
-
Details on F# Support in Rider
JetBrains’s developer evangelist Marteen Balliauw recently published more details about the F# support in Rider. Features are explained into more details than the general EAP announcement and also contains the plan for the next releases.
-
Zero Runtime Exceptions in Production with Elm
At QCon London 2017, Richard Feldman, software engineer at noredink and author of “Elm in Action” from Manning, explained how their decision to switch to Elm led to a 100,000 LOC system running in production with zero runtime exceptions since 2015. Here, we provide a brief summary of Feldman’s key points.
-
Building an F# Web Server with Freya
Freya is an F# web framework focusing on HTTP primitives and concurency. It doesn't include interface constructs such as templating. Marcus Griep presented Freya at F# eXchange 2017, where he explained its core model. He also showed the different mechanisms available for performance and concurrency, such as Hopac and Kestrel integrations.
-
.NET Core 2.0 Preview Released, Includes Visual Basic Support
Microsoft has announced the release of .NET Core 2 Preview 1. This brings .NET Core into compliance with .NET Standard 2 and adds Visual Basic support to .NET Core for the first time.
-
Being a Polyglot Programmer
Every programmer knows a langage or two. Being a polyglot programmer is a different mindset, fitting with the "Engineering yourself" principle. Zaiste, co-organizer of Polyconf, a conference dedicated to IT polyglotism, explains what it means to be a polyglot programmer, why it is useful, how to use it in your day-to-day job.
-
.NET Futures: Asynchronous Streams
Since async/await was announced for VB/C#, developers have been asking about an asynchronous version of IEnumerable. But until C# 7 and ValueTask, that was potentially challenging from a performance standpoint.
-
Emerging Technologies for the Enterprise Conference 2017: Day Two Recap
Day Two of the 12th annual Emerging Technologies for the Enterprise Conference was held in Philadelphia. This two-day event included keynotes by Blair MacIntyre (augmented reality pioneer) and Scott Hanselman (podcaster), and featured speakers Kyle Daigle (engineering manager at GitHub), Holden Karau (principal software engineer at IBM), and Karen Kinnear (JVM technical lead at Oracle).
-
C# Futures: Relaxed Overrides
A commonly requested feature in .NET is the ability to use covariant return types. An example of this would be overriding “virtual object Clone()” with “override Widget Clone()”. From a type safety perspective, this is perfectly acceptable, but C# doesn’t currently allow it.
-
C# Futures: Read-Only Local Variables
Not too long ago the proposal for read-only local variables was revived. This is a much more modest feature than the read-only references proposal, but the two are complementary.
-
C# Futures: Read-Only References and Structs
In C++ we have a feature known as “const”. This can be applied to parameters so that the caller knows that function will not modify the parameter and/or the object the parameter references. Under this proposal, C# would get something similar.
-
C# Futures: Nullable Reference Types
No, the headline isn’t a typo. One of the new proposals for C# is to assume that all reference variables are non-nullable by default. Under the new syntax, you would need to explicitly indicate when a reference variable is nullable, just as you do for value types.