As with all of the information about what Microsoft is up to in the development area, it had to be uncovered. In this case by Mary-Jo Foley who regularly scans and interprets the job adverts that Microsoft places. Now consider this for a moment - currently the only way to find out what Microsoft has planned for developers in the near future is to scan the specifications for the people they are hiring. If there ever was a sign that things aren't right between leaders and followers it has to be this. Could Microsoft be any worse at communicating with developers?
In this case the job advert was for programmers to work with the Office 15 on its programmability. One for a software engineer included:
Another made it clear that C# support wasn't going to be phased out:
Of course Office has never really made it into the .NET fold. After a confusing start, Office standardized on Visual Basic for Applications (VBA) and when .NET appeared it was reasonable to assume that VBA would be replaced by C# or VB .NET, but this never happened. The best .NET can offer is VSTO which allows the programmer to create add-ins or write applications that make use of Office components as COM objects. This is hardy the way to provide a macro language and so most Office users have stuck with VBA - the last outpost of classic VB and a huge anachronism.
If you would like to be informed about new articles on I Programmer you can either follow us on Twitter or Facebook or you can subscribe to our weekly newsletter.