Why Office 2010 and SharePoint 2010 are poised to unleash a new wave of developer innovation.
New APIs and native support for resources like the Ribbon UI, the Windows 7 Taskbar and parallelism boost native development.
With the release of Visual Studio 2010 and the .NET Framework 4, it's time for Visual Basic developers to start leveraging the new capabilities of Visual Basic 2010.
Stop me if you've heard this one before. Microsoft takes a popular application, builds it out into a platform, then refines and extends the opportunities for developers to code against it.
The language and library improvements outlined in Sumit Kumar's April 2010 article, "The Evolution of C++ in Visual Studio 2010," didn't alleviate a few readers' perceptions that C# and Visual Basic will win out at the expense of Visual C++/CLI.
Microsoft Office 2010, the new version of Redmond's flagship productivity suite, offers great value through important new features. But could they be doing better?
When the Visual Studio Team started developing the latest version of the product, we knew that improving support for Office and SharePoint was paramount.
Is it worth upgrading to the latest version of Visual Studio 2010, even if you're not going to move to .NET Framework 4? And if you are upgrading, what will you get?