Ken Ismert
kismert at gmail.com
Sun Jun 3 12:16:35 CDT 2007
(Martin) > here you go and I quote from a source who knows. > "VBA Will still be supported in Office" There you have it indeed. I share Martin's interpretation of that statement. (Shamil) > Have a look at article titled "Welcome to the 4% Operating System" on > this web site - http://www.richardgrimes.com/ Extremely interesting read. In theory, managed code should be as fast as unmanaged (see "Is Managed Code Slower Than Unmanaged Code?" on the same site). But, further reading ("Is .NET A Wrapper Around Win32?") reveals that the .NET framework itself is incorporating *more* unmanaged code with each release. Performance could be a legitimate reason for keeping the old Office code base, but there must be more going on. Inertia? Politics? However, if the 'rock' is performance, then the 'hard place' is security. The old Office file formats, and VBA, have proven to be fundamentally unsound. The response is new XML-based file formats, and 'sandboxing' VBA. How much of the old COM code is vulnerable is anyone's guess. An interesting project (that I don't have time for) is to use Richard's analysis tools to gauge the penetration of .NET code into the Office 2007 code base. If the new development is primarily unmanaged COM code, that would seem to bode well for native VBA. But if it is mostly in .NET, then VBA's place in the new order is less certain. -Ken