Visual Studio

Visual Studio 2010 comes in four flavors: Pro, Premium, Ultimate and Test Pro.  There are many new features including:

• Improved IDE with tear-away pages and multi-monitor support
• Search as you type
• Call hierarchy to see who calls what
• IntelliSense suggestion mode
• IntelliTrace Tivo-like debugging
• Extension manager
• Generate from Usage: use classes/members before defining them
• Live semantic errors (those colored squiggly lines)

Visual Studio 2010 Home Page
VS 2010 Product Highlights
What’s New in VS 2010
10 Cool Things About VS 2010

C# and Visual Basic

The main .NET languages C# and Visual Basic both saw significant improvements and new features including:

• Dynamic type and dynamic dispatch
• Named parameters and optional parameters
• Optional arguments and indexed properties
• Covariance and contravariance
• Statement lambdas
• Highlight all references of a symbol
• Implicit line continuations
• Office Automation APIs
• Auto-implemented properties

What’s New in Visual C# 2010
What’s New in Visual Basic 2010

.NET Framework 4

.NET Framework 4.0 is a major upgrade with many new features including:

• Support for the new language features mentioned above
• Support for IronPython, IronRuby, F# and M programming languages
• Oslo modelling platform
• Arbitrary-precision arithmetic types and complex numbers
• Parallel Extensions for multi-core and distributed systems

.NET Framework Home Page
What’s New in .NET 4
.NET 4 Code Examples

MSDN subscribers can download VS 2008 here.  Non-subscribers can download a 90-day free trial here.  The smaller, free versions of Visual Studio Express are here.  Or if you just want the .NET 3.5 framework, you can find it here.

Key features of VS 2008 and .NET 3.5 include:

• Multi-Targeting – Select the .NET version against which to build an application.  Thus, you can use VS 2008 to build .NET 2.0 or .NET 3.5 applications.
• Web Designer – Faster and much improved HTML designer with rich CSS support.
• AJAX – Now built-in to ASP.NET with many improvements.
• LINQ to SQL – Built-in OR/M (object-relational mapper) to model relational databases using .NET objects, then query and manage these databases using LINQ.
• Query Syntax – Declarative shorthand for expressing queries using the standard LINQ query operators.
• Anonymous Types – Concisely define inline types within code without having to explicitly define a formal class.  Anonymous types are particularly useful when querying and transforming data with LINQ.
• Lambda Expressions – Provide a more concise, functional syntax for writing anonymous methods.
• Extension Methods – Add new public methods to existing types without modifying or sub-classing the original type.
• Automatic Properties – Automatically create a private field and public get/set properties.
• Object and Collection Initializers – Shorthand code for initializing objects and object collections.

Note that VS 2008 runs fine on the same PC as VS 2005, so you can install and test VS 2008 without compromising your existing VS 2005 setup.  Or you can use VS 2008 and multi-targeting to build and maintain your existing .NET 2.0 applications.  Also, .NET 3.5 is built upon the .NET 2.0 framework, so your .NET 2.0 applications should run fine on PCs with only .NET 3.5 installed.

VS 2008 and .NET 3.5 are terrific upgrades that continue to advance the .NET development environment.  The only negative is that once again, Microsoft is releasing .NET 3.5 as a separate download and not as a required component of Windows Update.  As a result, it will be at least 2-4 years before software developers can expect a majority of Windows users to have .NET 3.5 installed on their PCs, which is a real shame.

The death knell for Visual Basic is premature, but it’s true that VB has deviated from its original vision as an “Application Construction Kit” for the masses and has lost significant market share as a result.  

Tim Anderson summed it up best:

It sounds like perfection.  Microsoft had perhaps the largest number of developers in the world hooked on a language which in turn was hooked to Windows.  Yet Microsoft took this asset of incalculable value and apparently tossed it aside.  Back in 2002, Microsoft announced that the language was to be replaced by something new, different and incompatible.  That caused rumblings that continue today.  Developers expressed emotions ranging from frustration to anger.  They felt betrayed.

Much has been written lately about the fall of Visual Basic, triggered by an Evans Data survey indicating that VB use has dropped 35% in the past year, and other language surveys show VB falling behind its brother C# and market leader Java.

The problem is simply that when Visual Basic became VB.NET, it became a “real” programming language for trained developers, no longer the layman’s “Application Construction Kit” of its original vision.  As such, there’s little to positively distinguish VB from the other .NET programming languages, especially the superior and more popular C#.  The result is an expected drop in market share. 

Perhaps next-generation Web development environments like Popfly and Silverlight will fill the gap left by VB.  And there is a concerted effort including a web petition to convince Microsoft to support and upgrade the last “simple” version of Visual Basic, VB6.  This support is unlikely, however, and VB’s reign as “programming language for the masses” is over.

Humble Beginning

Alan Cooper is widely regarded as the father of Visual Basic.  In 1987, Cooper was a director at Coactive Computing Corporation where he developed “Tripod,” an improved shell/desktop for the fledgling Windows operating system.  After initial testing, Cooper realized that “every user would need their own personal shell, configured to their own needs and skill levels.”  The idea of a “shell construction set” was born.  There would be a palette of tools and controls, which users could drag & drop onto forms to create their custom shell.

Cooper began shopping the product around Silicon Valley seeking a publisher.  There was little interest until March 1988 when Cooper showed a prototype to Microsoft CEO Bill Gates.  Visionary that he is, the 32-year-old billionaire immediately saw Tripod’s potential.  Gates declared that Tripod was “cool” and would have significant impact across Microsoft’s entire product line.  In a few months the deal was done, Tripod became Microsoft’s “Ruby,” and Cooper assembled a team of engineers to deliver a commercial product.

The original intention was to ship Ruby with Windows 3.0 as a more powerful shell, but Microsoft instead decided to use the OS/2 shell, which Microsoft owned at the time from its deal with IBM.  Microsoft decided to delay Ruby and convert it from a shell construction set for all users to a visual programming language for professional developers by adding QuickBasic.  At first, Cooper was upset with Microsoft’s decision and argued against it.  However, after seeing the power of the eventual product, Cooper soon became an “enthusiastic Visual Basic supporter.”

An Empire Rises

Visual Basic 1.0 for Windows was first released on May 20, 1991 at the Windows World convention in Atlanta where Gates described it as “awesome.”  InfoWorld Magazine described Visual Basic as a “stunning new miracle” that would “dramatically change the way people feel about and use Windows.”  Stewart Alsop wrote in the New York Times that Visual Basic is “the perfect programming environment for the 1990s.”

VB version 3 (1993) added database access tools and Object Linking and Embedding (OLE).  Visual Basic for Applications (VBA) was released in 1993 to replace the disparate macro features across Microsoft’s product line and has since become the de facto standard for application programming in Microsoft Office and other products. 

VB4 was released in 1995 to support the 32-bit Windows 95 operating system.  VB5 was released in 1997 with significant improvements to the user interface, ability to create true executables and custom controls, and support for Microsoft’s Active-X technology.  It also dropped support for the 16-bit Windows 3.x operating system.

VB6 was released in 1998 as part of Visual Studio 6.0 that also included Microsoft’s Visual C++ development environment.  VB6 improved database access, added Internet features, language improvements and wizards.  Many organizations still use VB6 today.

Microsoft surveys in the late 1990s showed that nearly two thirds of all business application programming on Windows PCs was done in Visual Basic.  VB’s overwhelming success was largely because it made Windows programming much easier.  Prior to VB, Windows programming required mastery of the massive and complex Win32 APIs and took hundreds of lines of code to create even simple screen elements.  VB eliminated the need to write lengthy code for the user interface, allowing developers to focus on business logic and produce usable Windows applications relatively quickly. 

World-renowned Windows programming expert Charles Petzold told the New York Times, “For those of us who make our living explaining the complexities of Windows programming to programmers, Visual Basic poses a real threat to our livelihood.”

.NET Pulls Out the Rug

In the late 1990’s as the Internet was exploding, Microsoft had just successfully fought off a full frontal assault on its market dominance by killing the Netscape Web browser with its free Internet Explorer.  But Microsoft was facing a host of new challenges, including serious problems with COM, C++, DLL hell, the Web as a platform, security, and strong competition from Java, which was emerging as the go-to language for Web development. 

Microsoft’s response was .NET, an object-oriented development environment and framework that provides a highly-functional abstraction layer between the operating system and programming language.  Microsoft announced .NET to the world in June 2000 and released version 1.0 of Visual Basic .NET and the .NET framework in January 2002.  Microsoft also labeled everything .NET including Office to demonstrate its commitment and dominance on this new thing called the Web. 

Unfortunately for VB6 developers, the .NET object-oriented platform is far different than the procedural VB6 programming language, and so there was no easy way for developers to migrate their legacy VB6 code to VB.NET.  Even though a few automated tools emerged to aid the conversion, due to the subtleties and intricacies of the languages, a significant amount of manual, error-prone labor was required.  For larger projects, one would be better off re-writing the application from scratch in .NET using object-oriented architecture and best practices, than performing a mechanical port of VB6 code to VB.NET.

But starting over from scratch means evaluating all options on the table.  And to most “Mom & Pop” developers, Visual Basic .NET appears to be an enterprise product with an enterprise price tag, with significant overhead required in terms of programming skills and computer resources.  So instead of trying to manage the complicated move from VB6 to VB.NET, many VB6 developers moved their applications to the Web, using Java, JavaScript, Perl and PHP.  As a result, millions of developers have left the Microsoft mothership and are unlikely to return.

Don’t worry, be happy, VB fans.  Programming languages never die, they just fade away.  My COBOL/RPG2 programming buddies were working hundred-hour weeks during Y2K!

VB is Not R.I.P.

Much of the negative press lately about VB derives from the Evans Data survey indicating that overall use of Visual Basic has dropped 35% in just one year, including a 26% drop for VB.NET specifically.  As a result, Java now leads with 45% market share(developers using Java some of the time), followed by C/C++ at 40%, C# at 32%, and Visual Basic at 21%.

Although a 35% drop in market share is significant, it’s too early to write the Visual Basic obituary.  Most companies would love to own 21% of a multi-billion-dollar market, though that may not be good enough for Microsoft.  But combined with C# and managed C++, the Microsoft .NET family still commands half the software development market.

What is clear is that Visual Basic is no longer the programming language for the masses of its original vision.  As a result, VB.NET will have to compete with the other .NET and Web languages on its own merits.  With its wordy syntax and second-class status relative to big brother C#, it’s unlikely the Visual Basic empire will rise once again.  But Visual Basic will continue to be an effective Windows development platform for many years to come.