In a recent blog post the Visual Basic team let slip an announcement that Visual Basic and C# would be getting a new syntax for asynchronous programming. Built on top of the Task Parallel Library that was introduced in .NET 4, this adds the Async and Await keywords to both languages.
In 2009 Microsoft’s Lucas Bolognese announced a commitment to co-evolution for C# and Visual Basic. And the productization of F#, some have assumed it extends to that language as well. But by only offering C# in the initial release of WP7, this promise has been brought into doubt.
Optional parameters have always been part of .NET, but with C# unwilling to support it, using them was generally considered taboo unless work with COM libraries. Now that C# 4 does support them, we are starting to see them used for a lot more than just legacy code. Other uses include interoperability with dynamic languages, immutable data structures, and various parts of ASP.NET MVC.
Visual Basic has always been on the fence between static and dynamic typing. In the beginning VB supported late binding, which is known today as “duck typing”. Through the years it has adopted support for stricter typing, though recently it has swung the other way with full support for the dynamic language runtime.
An IT services provider company has migrated an ERP application totaling 950,000 lines of VB6 code to .NET in 9 months.
Visual Basic for Applications is a dead-end and Visual Studio for Applications isn’t ready for prime time, leaving developers in the uncomfortable position of trying to mix .NET code with legacy VBA macros. Fortunately Visual Studio Tools for Office makes it relatively painless.
Visual Basic 10, to be released with .NET 4.0 and Visual Studio 10, is adding support for collection and array initializers. While these are similar to what we already have in C#, there are minor enhancements such as support for extension methods and improved type inference.
Many have wondered why Microsoft is giving a different treatment to VB.NET compared to C#, why VB.NET developers are paid less than C# ones and if they should worry for their future or not. In a podcast, Lisa Feigenbaum, PM in .NET Managed Languages Group, assures the VB.NET community that VB definitely has a future.
C# added auto-implemented properties in version 3, but Visual Basic was unable to match them at that time. With the impending release of .NET 4.0, VB has caught up in this area, but with a distinctive twist.
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.
Pattern matching may seem like an alien concept to developers who focus on C# and VB style languages, but it shouldn’t be. Ultimately it is just a refinement of the case statement, which itself is a refinement of if-else-if blocks. This piece takes a brief look at that transition and how F#’s pattern matching can be applied to VB and C#.
Gizmox announces the release of a free preview version of its Visual WebGui, version 6.4, product. VWG promises a point-and-click tool for RIA development (DHTML or Silverlight) that requires no HTML, CSS, or XAML coding; and that can be integrated with Photoshop, Expression Blend, and Flash CS.
At the 2008 PDC, Microsoft promised language parity between Visual Basic and C#. What that means for .NET 4 was enumerated during the Lang.NET keynote. Briefly, this is what you can expect to see.
Visual Basic 10 will have an improved compiler that makes underscores optional for most line continuations. This represents a significant change for VB, traditionally a line-terminated language.