Visual Studio 2017 is coming on March 7


Join us at 8:00 AM PST on March 7 for a two-day online event celebrating the launch of our latest version as well as 20 years of Visual Studio. Watch the live stream featuring Julia Liuson, Brian Harry, Miguel de Icaza, and Scott Hanselman as they share the newest innovations in Visual Studio, .NET, Xamarin, Azure, and more. After the keynote, Microsoft engineers will lead interactive technical demo sessions to help you get the most out of Visual Studio 2017 and the rest of our tools and platform.

On March 8, we’ll help you get productive even faster by hosting a full day of live interactive trainings. Don’t forget to click Save the Date above and sign up for email reminders!

Whether you are new to our tools or have been with us since the beginning, we’d love to hear and share your Visual Studio story. Share a photo of memorabilia or a short video clip of your story with Visual Studio on Instagram or post your story on Twitter and Facebook using #MyVSstory. Check out Julia’s launch event announcement for more details.

Microsoft’s Channel 9 introduces .Game, a new series focused on game development using .NET


Microsoft has introduced a new show to its Channel 9 video platform aimed at teaching and showing off Microsoft’s products and services. The new show is called .Game and aims to teach people how to develop games using .NET.

In this new series, viewers will be able to watch along and discover how game development works and how to do it themselves. The first episode of the show is already available and focuses on the basics with Unity, a popular game engine.

The above video introduces the .Game show. Stacey Haffner explains that the show will provide tips and tricks, as well as access to files on Github to make use of, in addition to resources and other tutorials that people may find helpful when it comes to game development.

Microsoft Orleans


Orleans is a framework that provides a straightforward approach to building distributed high-scale computing applications, without the need to learn and apply complex concurrency or other scaling patterns. It was created by Microsoft Research and designed for use in the cloud.

Orleans has been used extensively in Microsoft Azure by several Microsoft product groups, most notably by 343 Industries as a platform for all of Halo 4 and Halo 5 cloud services, as well as by a growing number of other companies.

Scalable by Default
Orleans handles the complexity of building distributed systems, enabling your application to scale to hundreds of servers.
Low Latency

Orleans allows you to keep the state you need in memory, so your application can rapidly respond to incoming requests.

Simplified Concurrency
Orleans allows you to write simple, single threaded C# code, handling concurrency with asynchronous message passing between actors.

Support Ending for the .NET Framework 4.0, 4.5 and 4.5.1 on Tuesday

In less than a week Microsoft will formally end support for versions 4.0, 4.5, and 4.5.1 of the .NET Framework. Users should upgrade to a later version such as the slightly incompatible .NET 4.5.2.

Before we move on, it should be noted that this only affects the 4.x series. The much older .NET 3.5 SP 1 will continue to be supported. In this context, support means having access to technical support, security updates, and hotfixes.


When upgrading to .NET 4.5.2, ASP.NET developers may see a compatibility issue. Though considered a security risk, developers previously had the ability to disable the view state message authentication code by setting enableViewStateMac to false at the application or page level. This is no longer permitted.

If you recompile your application for .NET 4.5.2 and use the DataObject.GetData to read from the clipboard, you could also run into problems.

For apps that target the .NET Framework 4 or that run on the .NET Framework 4.5.1 or earlier versions, DataObject.GetData retrieves HTML-formatted data as an ASCII string. As a result, non-ASCII characters (characters whose ASCII codes are greater than 0x7F) are represented by two random characters. For example, é (0xE9) is represented by é (0xC3 0xA9).

For apps that target the .NET Framework 4.5 or later and run on the .NET Framework 4.5.2, DataObject.GetData retrieves HTML-formatted data as UTF-8, which represents characters greater than 0x7F correctly.

If you choose to migrate to .NET 4.6, the breaking changes are more significant. See the Application Compatibility in the .NET Framework 4.6 guide for details.


If you have automatic updates turned on, your Windows Azure Guest OS will be upgraded to .NET 4.5.2 in January.

.NET Core and ASP.NET Launches a Beta Bug Bounty Program

BugBountyProgramToday, with great excitement, we announce an introductory 3 month bug bounty program for .NET Core and ASP.NET, our new open source, cross platform runtime and web stack. The program encompasses the latest beta version, beta 8 and any subsequent beta or release candidates released during the program period.

We recognize that you, our customers, rely on our platforms and development tools to write your own software. The more secure we can make our frameworks the more secure your software can be. We take your trust seriously and this program is part of our investment in improving the security of our frameworks on all platforms. Starting a bounty program during our beta period allows us to address issues quickly and comprehensively. We are able to reward and recognize security researchers for their hard work and for any qualifying security bugs they report to us under the aegis of the program. This is the right thing for our customers and for the security researcher community.

The bounty includes all supported platforms .NET Core and ASP.NET runs on; Windows, Linux and OS X. However with the first eligible release, beta 8, we are excluding the networking stack on Linux and OS X. In later beta and RC releases, once our cross platform networking stack matches the stability and security it has on Windows, we'll include it within the program. When this happens we'll update the bounty terms and conditions and make a blog post on this blog. The ASP.NET web site has instructions on how to install beta 8 on Windows, Linux and OS X. Windows researchers can use Visual Studio 2015, including the free Visual Studio 2015 Community Edition, after following the instructions to update the web tooling. The source for .NET Core can be found on GitHub at The source for ASP.NET v5 can be found on GitHub at

We encourage you to read the program terms and FAQs before beginning your research or reporting a vulnerability. We would also like to applaud and issue a hearty and grateful thanks to everyone in the community who has reported issues in .NET and ASP.NET in the past. We look forward to rewarding you in the future as we take .NET and ASP.NET cross platform.

Microsoft taps open source LLVM compiler for cross-platform .Net


Does it make sense to build something from scratch when there's a perfectly good solution available - especially if it's open source? Once upon a time, Microsoft's default was to build its own rather than use someone else's work; now, the reverse is becoming true.

Consider the LLILC project. Rather than reinvent the wheel, Microsoft's new compiler for its CoreCLR .Net runtime leverages an existing cross-platform compiler framework: LLVM. Now six months into the project, its maintainers -- a foundation comprised largely but not exclusively of folks from Microsoft -- reports "great progress" with LLILC, but also "much still to do."

LLILC is currently capable of performing just-in-time compilation ("jitting") of "all the [.Net] methods in some fairly complex scenarios." How complex? "Roslyn is a C# compiler written entirely in C#," the dev team states, "and LLILC can jit Roslyn compiling itself."

LLILC isn't yet replacing CoreCLR's original jitting mechanism; instead, the LLILC and CoreCLR jit engines run side by side. If the first one encounters something it can't handle, it's handed off to the second engine, which allows the compilation pipeline to continue running. Full garbage collection and proper exception handling support are two features lined up for the next phase of work.

The .Net Foundation, the project's official maintainer, features team members and contributors from far and wide - GitHub and the Debian Mono group have advisers on board, for instance -- but is composed mainly of folks from Microsoft and is being used to sponsor a technology Microsoft itself invented. That said, those working on LLILC are shaping their contributions to fit LLVM, rather than trying to rework LLVM to fit LLILC's needs.

"Our intention has always been to upstream as quickly as possible," the project team writes. "We're still working on making good at that intention, but so far the number of changes we’ve had to make are fairly modest."