While all of the recent news has been focused on C# and Windows 10, F# isn’t standing still. Along with Visual Studio 2015 RC is the latest version of F# 4.0.
Microsoft has announced the release of a native Visual Studio application for Windows, Mac OS X, and Linux.
Microsoft has completely rewritten the build server in Team Foundation Server and Visual Studio Online. The new tool completely eliminates the massive XAML-based Windows Workflow files that were used as build definitions.
Universal XAML isn’t just an application UI toolkit, it is being used throughout Windows 10 for OS programs. As such, cross-platform consistency and performance are of upmost concern. To address this, new features such as compile-time data binding has been added.
Depending on who you ask, IoT is something brand new and revolutionary or just a natural progression of what we’ve been doing for decades. The truth is somewhere in the middle; consumer devices replacing the simplistic, mass produced sensors and expensive aviation-grade components. With this in mind, Kevin Miller of Microsoft offers these basic guidelines for starting an IoT project.
A big emphasis for many developers, especially those writing games or working on pure number crunching, is raw performance. One way to get more performance out of C# is to avoid allocating memory without having to copy structs instead. The next proposal shows how C# can expose the CLR managed pointer support to do just that.
Microsoft's premier developer conference began today with several announcements that will affect all developers whether they are formally targeting Windows or not.
Probably the most common error type in .NET is the Null Reference Exception. The root cause of this error is C#’s inability to express the concept of non-nullable references, which in turn makes compiler-enforced null checking it too burdensome. To address this problem, there is a proposal for mandatory and explicitly nullable references.
Once again, Visual Basic has been brought back from the brink of deprecation. Reversing a previous decision, VB will be fully supported in ASP.NET 5 including cross-platform.
With C#6 nearing completion, plans are already being laid for C# 7. While nothing is definite yet, they are starting to categorize proposals in terms of “interest and estimated plausibility”. In this series, we’ll be looking at some of the proposals starting with language support for tuples.
PowerShell Tools for Visual Studio is a Visual Studio extension that brings the power of Visual Studio to PowerShell developers. Adam Driscoll, the original creator of this extension, got help from Microsoft over the past couple of months. The result is a new release, v3.0.108, offering 64-bit and remote session support, among other improvements.
A question that keeps coming up is whether or not Blend should be integrated into Visual Studio. The current thought is that it is still better to have separate tools, one focused on UI design tasks and one focused on application development. But that doesn’t mean both can’t be improved.
One of the limiting factors in WPF development is the fact that it is a core component. Since it is shipped with .NET itself, and often the OS, the compatibility requirements are extremely high. By moving to a NuGet distribution model, Microsoft is willing to ease the capability requirement and attempt riskier changes.
Building on its Unity game engine support, Microsoft has announced that it is broadening this support to include Unreal Engine and Cocos2D.
Despite rumors to the contrary, WPF development at Microsoft isn’t dead. There are four major areas of investment for WPF in .NET 4.6 and beyond: Performance, DirectX Integration, Supporting Modern Hardware, and Tooling.