InfoQ Homepage C# Content on InfoQ
-
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.
-
.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.
-
.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.
-
.NET Futures: Type Classes and Extensions
Another feature being considered for future versions of .NET are type classes. Referred to as “shapes” in the Shapes and Extensions proposal, they would greatly increase the capabilities of .NET generics.
-
.NET Futures: Multiple Inheritance
A controversial new proposal for .NET suggests the introduction of a limited form of multiple inheritance via abstract interfaces. This feature was inspired by Java’s default methods.
-
.NET Core Tools 1.0 Released with Full C# Support
The .NET Core Tools has produced its first 1.0 release. Focused on C#, the tools provide .NET Core developers easy-to-build applications for .NET Core and ASP.NET Core. While their release coincides with the launch of Visual Studio 2017, this is a multiplatform toolset supporting Windows, Linux, and Mac OS systems.
-
Microsoft's Plans for the Future of .NET
Microsoft develops C#, Visual Basic, and F# in public but doesn't always share its plans for these popular languages. Mads Torgersen has provided some new guidance on where Microsoft plans to take these languages in the future.
-
Testimonial on Using F# by Microsoft's Project Springfield Team
Project Springfield is a fuzz testing service for finding security critical bugs in software. William Blum, principal software engineering manager on the Springfield team at Microsoft Research, explains how adopting F# helped the team build the cloud service.
-
Developer Panel Discusses Microservices, Containers and Serverless at Microsoft Connect
A developer panel was held at Microsoft Connect() following the multiple annoucements of new features and releases. Microservices and containers are in the center of the discussion, along with Azure, serverless architecture and developer tooling.