In a very small announcement by Developer Division’s Marketing and Communications Manager Rob Caron, Visual Studio 2010 and .NET Framework 4.0 is set to be officially launched April 12, 2010 and not March 22 as previously announced. However, the date for release to manufacturing (RTM) still remains unknown.
Assemblies built in Silverlight 2 and 3 are not binary compatible with the .NET Framework, so if you want to share code you need generally need to dual-compile. With Siverlight 4 and .NET 4, you will be able to use some Silverlight-based assemblies from within .NET 4.
At PDC 2009, Michael Shim and Rob Relyea presented Microsoft’s plans for the future of XAML. Long term, they plan on unifying the various XAML languages and parsers, but for now developers will only get XAML 2009 for non-UI technologies like Workflow Foundation. The new parser, on the other hand, will bring new functionality to everyone who needs to analyze, manipulate, or generate XAML.
In .NET 4.0, Microsoft is replacing .NET’s Code Access Security (CAS) with a new security model inspired by Silverlight. This rather than complex link demands, code is categorized into three easy to understand levels with partially trusted code being unable to call fully trusted code except via carefully designed gateway functions.
WPF 4.0 will be adding new controls, Pixel Shader 3.0, and a completely rewritten text rendering pipeline. These and other features will find their way into Visual Studio 2010, expected early next year.
Previews of IronPython for .NET 4 have been shipping along with VS 2010, but that does not mean the two are tied together. We break down the plans for delivering IronPython to .NET developers.
Microsoft has released a new version of .NET 4.0 Beta 1, one that incorporates STM.NET, the Software Transactional Memory. STM is an alternative mechanism to lock-based synchronization used to control the concurrent access to shared memory.
Erik Meijer and Wes Dyer have created the .NET Reactive Framework (Rx), the mathematical dual of LINQ to Objects, allowing programmers to use LINQ over events. Erik and Brian Beckman demonstrate that IObservable is a continuation monad.
Not everything planned for Visual Studio 2010 made it in beta 1. This includes some important features for ORM fans. Entity Framework CTP 1 includes support for Self Tracking Entities, POCO Templates, and support for EDMX-free coding.
Microsoft announced System.Data.OracleClient will be marked obsolete in .NET 4.0 and removed from future releases. OracleClient is the ADO.NET provider for Oracle developed by Microsoft and shipped as part of the .NET FCL. Its absence will be an impediment to future upgrades for the many small projects using this provider for Oracle data access.
A new article by David Chappell describes how BPM engines are different from plain programs written in Java, C#, etc. and the ways Windows Workflow Foundation can be used to build workflow applications.
In this interview Eric Nelson talks about what’s coming in VS 2010, the C# – VB.NET convergence, the introduction of Parallel as a library, and Azure cloud computing.
Creating wrapper functions for pre-existing stored procedures is surprisingly difficult in .NET. Stored procedures have certain calling conventions that aren’t generally used in the .NET Framework and many of them are not supported at all. For example, C# doesn’t support optional parameters and neither .NET language supports optional parameters on nullable types.
.NET 4 will have new types to support building cancellation-aware applications and libraries. The new CancellationToken, CancellationTokenSource, and cancellation exception types provide a cooperative cancellation framework.
Damien Guard of Microsoft’s Data Programmability has posted a rather long list of the changes to LINQ to SQL. While they are still committed to Entity Framework over the long run, this will do much to alleviate the fear LINQ to SQL will be completely neglected in the mean time.