vba VBA的未来是什么？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/1112491/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
What Is the Future of VBA?
提问by Rook
With the new 2007 versions of MS-Office, Microsoft started to "threaten" VBAwith VSTA. Since VBA is pretty commonly used, what do you believe its future is in terms of scripting development for the next 3-5 years?
随着新的 2007 版 MS-Office，微软开始用VSTA来“威胁” VBA。由于 VBA 非常常用，您认为它在未来 3-5 年的脚本开发方面的未来是什么？
Or, will it be killed suddenly, like VB6?
或者，会不会像VB6一样突然被杀掉？
Autodesk also dropped it(kind of) upon hearing news from MS.
Autodesk在听到 MS 的消息后也放弃了它（有点）。
回答by p.campbell
I'd suggest that VB6 wasn't killed suddenly. Official MS support, perhaps, but still the community is alive for both VB6and VBAhere on SO.
我建议 VB6 不会突然被杀死。也许是官方的 MS 支持，但社区仍然在 SO 上为VB6和VBA提供支持。
As with any technology with a WIDE user/customer/3rd party vendor base, it will take a long time for VBA as a scripting technology to fade away. I would imagine that it will take years for its successor to fully overtake VBA.
与任何拥有广泛用户/客户/第 3 方供应商基础的技术一样，VBA 作为一种脚本技术需要很长时间才能逐渐消失。我想它的继任者需要数年时间才能完全超越 VBA。
回答by Ian Digby
Agree with Dick Kusleika about deployment
同意 Dick Kusleika 关于部署的意见
The problems with deprecating VBA are:
弃用 VBA 的问题是：
- Ease of deployment
- Visual Studio - another IDE to learn
- For the huge base of working, business-critical VBA apps, where nothing will be added by .NET, why would one want to spend the effort and time migrating?
- With VBA, non-developers can knock up quick useful applications within Excel/Word etc. You can't do this with .NET/VSTO.
- 易于部署
- Visual Studio - 另一个要学习的 IDE
- 对于大量工作的关键业务 VBA 应用程序，.NET 不会添加任何内容，为什么要花费精力和时间进行迁移？
- 使用 VBA，非开发人员可以在 Excel/Word 等中快速创建有用的应用程序。使用 .NET/VSTO 则无法做到这一点。
回答by Dick Kusleika
It will die, IMO, but not suddenly. Excel used to have a macro language called XLM - basically a keyboard playback on steroids. XLM is still supported, and there's easily a dozen people who use it. That's why I think VBA will be around for quite a while. It won't be updated, supported, and maybe not even acknowledged, but it will be available.
IMO，它会死，但不会突然消亡。Excel 曾经有一种称为 XLM 的宏语言 - 基本上是类固醇的键盘播放。XLM 仍然受支持，而且很容易就有十几个人在使用它。这就是为什么我认为 VBA 会存在很长一段时间。它不会被更新、支持，甚至可能不被承认，但它会可用。
Sooner or later MS will integrate .NET with Office apps and fewer people will care about VBA. Right now, I can put some VBA in an Excel spreadsheet, send it to a client, and deployment is done. I can tell the IT department it's an Excel workbook with macros, and they don't feel threatened because they don't know any better. When .NET has deployment options that simple, I'll use it instead. That day will come and VBA will slowly start fading away.
MS 迟早会将 .NET 与 Office 应用程序集成在一起，而很少有人会关心 VBA。现在，我可以将一些 VBA 放入 Excel 电子表格中，将其发送给客户端，然后部署就完成了。我可以告诉 IT 部门这是一个带有宏的 Excel 工作簿，他们不会感到受到威胁，因为他们不知道更多。当 .NET 具有如此简单的部署选项时，我将改为使用它。那一天终将到来，VBA 将慢慢开始消失。
回答by shahkalpesh
The language has changed & the way things were done (i.e. drag/drop form, create a macro, modify a few line & you are done) will also change.
语言发生了变化，事情的完成方式（即拖放表单、创建宏、修改几行并完成）也将发生变化。
It won't remain a tool, which a non-developer will find easy to use.
它不会仍然是一个工具，非开发人员会发现它易于使用。
Object model should remain same for basic stuff (Workbook, Worksheet, Range) etc.
New set of things will get added & that will change the object model & hence new learning (e.g. Ribbon Interface)
对于基本的东西（工作簿、工作表、范围）等，对象模型应该保持不变。
新的东西将被添加，这将改变对象模型，从而改变新的学习（例如功能区界面）
Not to forget, .net brings in its own concepts/complexity.
不要忘记，.net 带来了它自己的概念/复杂性。
