The following is an extract of an announcement that went public yesterday.  It shows again the momentum around migrations.  I am currently at PDC in Los Angeles and talking to ISVs, that are current VBA licensees, about how to approach the transition to the new technology.  They all seem to like the automated migration approach in which they provide their customers with tools to help automate the process.  What do you think?  Let me know, let's explore the issue...

“ VSTA consists of an IDE used by ISVs to build VSTA support into an object model they can expose in their application, a runtime engine, and an end-user IDE which communicates with the object model. It includes a software development kit (SDK) for integrating a customer interface object model into the ISV application and an end-user IDE incorporating VB .NET and C#. The application then uses the .NET Framework Common Language Runtime (CLR) for development and production.

Recently, the level of investment made by VBA partners in their .NET applications has increased considerably. Many will decide to integrate VSTA into their existing VBA-enabled products and that, in turn, will create a strong demand among their customers for the migration of their VBA code to the .NET Framework.

ArtinSoft now provides its migration technology and expertise to ISVs who have integrated Microsoft VBA into their products and choose to integrate VSTA into their .NET applications. We have designed this new solution to meet the migration needs of VBA partners worldwide. The core of the solution is a recasting of the ArtinSoft VB Upgrade Companion in order to process VBA projects effectively and then efficiently convert them into fully natural VSTA solutions through the migration and restructuring of their original code. Summit Software , which has supported hundreds of VBA partners since 1996, has provided invaluable input into the design of our new solution. We are currently working closely with Summit to deliver this support program to the VBA community. “