InfoQ Homepage .NET Content on InfoQ
-
C# Futures: Defer
Best known for its use in Go and Swift, C# proposal #1398 seeks to add defer statements. If you are not familiar with the concept, it can be summarized as a finally block appearing at the beginning of some code instead of the end.
-
Update on IAsyncDisposable and IAsyncEnumerator
Since InfoQ last covered the async streams proposal, some changes have been made to the design. Most notably is the use of the lightweight ValueTask object.
-
System.Collections in .NET Core 3.0
If you look through the list of issues tagged for System.Collections in .NET 3.0, you’ll find both proposals that were accepted and rejected. In this report we’ll cover some of the highlights.
-
F# 4.6 Introduces Anonymous Record Types
The next release of F#, F# 4.6, will most notably bring anonymous record types and structs to the language, along with a few additions to the standard library.
-
The Pure Attribute in .NET Core
The Pure attribute was added to .NET in version 4 as part of the Code Contracts initiative to help developers distinguish between code that free from side effects from other code. While the Code Contracts project is over, the Pure attribute continues to see life in .NET Core.
-
SQL Server and .NET Core 3.0
In our last article we looked at System.Data in .NET Core 3.0. Now we turn our attention to System.Data.SqlClient, which is the SQL Server driver.
-
System.Data in .NET Core 3.0
While it doesn’t get a lot of attention, System.Data is crucial for any sort of relational database access in .NET. Also known as ADO.NET in honor of its predecessor, ActiveX Data Objects, System.Data provides a generic framework upon which .NET database drivers can be built. It won’t see a lot of changes in .NET Core 3.0, but for the first time in years we see new methods in a foundational class.
-
C# 8: Generic Attributes
Attributes have been part of .NET since the beginning. As such, they were created before generics were introduced and never quite caught up. Though supported by the CLR, before this proposal C# didn’t offer the ability to use generic attributes.
-
C# 8: Caller Expression Attribute for Assertions and Automated Testing
Currently C# supports caller info attributes for file name/path, line number, and the name of the calling method or property. With the Caller Expression Attribute proposal, expressions are added to the list.
-
C# 8: Type Inference for the New Keyword
In many situations, there is only one possible type allowed in a given place. And yet C# still requires you to explicitly list the type. If the Target-typed `new` expression proposal is adopted, such boilerplate code will no longer be necessary.
-
ASP.NET Core 3.0 Projects Go on a Diet
Microsoft.AspNetCore.App, the primary dependency for more ASP.NET Core projects, has 150 explicitly listed dependencies. In order to improve long-term supportability, over 30 of these will be dropped in ASP.NET Core 3.0.
-
EF Core Database Providers
When EF Core did their big rewrite between the 1.x series and 2.0, all of the EF Core database providers were broken. Since then various development teams, both private and commercial, have been working on filling in the gaps.
-
Entity Framework 6.3 and EF Core 3.0 Roadmap
Though separated from the .NET Core release cycle, EF Core is developing its 3.0 roadmap. Along with it are some important changes to the original Entity Framework.
-
Partial Support for Spatial Queries in EF Core 2.2
Entity Framework Core 2.2 adds support for spatial queries using the NetTopologySuite.
-
First Look at .NET Core 3.0: C# 8, WPF, Windows Forms, and More
The next major version of .NET Core has recently entered Preview stage. .NET Core 3.0 will include support for building desktop apps using Windows Presentation Foundation (WPF), Windows Forms (WinForms), Entity Framework (EF), ASP.NET Core 3.0, C# 8, and .NET Standard 2.1.