InfoQ Homepage C# Content on InfoQ
-
Using C# to Target GPUs
The new Hybridizer technology provides C# developers with a way to target the CUDA platform and take advantage of GPUs for increased performance. Thanks to Hybridizer, developers are not forced to use C or C++ to write high-performance GPU code.
-
5th Update to Visual Studio 2017 Expands Debugging Tools
The fifth update to Visual Studio 2017 has reached general availability and brings another batch of improvements to Microsoft's popular developer tool. Version 15.5 focuses on improvements to the debugger tools, faster C#/VB solution loading times, and expanded C++17 support.
-
Realm Extends its .NET Stack Support with Realm .NET
After introducing support for .NET Core last summer to build mobile applications using C#, Realm announced Realm .NET, a set of new components that allow developers a better integration with their .NET stack.
-
Microsoft Previews Nullable Reference Types in C# 8
Microsoft has made available Nullable Reference Types as preview for developers who want to try the new feature and provide feedback.
-
Catching up with C# 7.1 and C# 7.2
Back in August, C# 7.1 was quietly released along with Visual Studio 15.3, but it’s not quite ready. In this report we’ll look at a subtle compiler bug and what’s next in store for the soon to be released C# 7.2.
-
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.