安装了 Office 2010 和 Office 2007 的 Visual Studio 2010 RC
我在 Windows XP 开发计算机上安装了 Visual Studio 2010、Office 2007 Professional 和 Office 2010 Professional。我正在尝试为 Office 2007 开发几个插件；不过，我更喜欢在日常工作中使用 Office 2010。
如何设置 Visual Studio 2010 以在按“调试”键时安装加载项并打开 Word 2007？目前，Word 2010 可以打开，但无法识别该加载项。除非迫不得已，否则我愿意保留安装 Office 2010。
I have Visual Studio 2010 installed on my Windows XP development machine along with Office 2007 Professional and Office 2010 Professional. I am trying to develop several add-ins for Office 2007; however, I prefer to use Office 2010 on a day-to-day basis.
How do I set Visual Studio 2010 to install the add-in and open Word 2007 when I press debug? Currently, Word 2010 opens, but does not recognize the add-in. Unless I have to, I would like to keep Office 2010 installed.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不知道您的问题的具体答案，但我正在运行 Office 2010，并且仍在从事 Office 2007 加载项开发。
我对这个问题的解决方案是虚拟机。我不在笔记本电脑的主要操作系统上进行任何开发工作。我什至没有安装 Visual Studio，但我正在运行 Office 2010，并且到目前为止我非常喜欢它。
为了进行开发，我有数十个不同的虚拟机，它们具有各种操作系统和 Office 版本配置以及我需要集成的其他 3rd 方软件。我目前使用的是 Windows 7 和新版本的 Windows Virtual PC，但我在使用 Windows XP 和 Virtual PC 2007 时就开始了这种做法。
这样做的一个好处是，如果我的其中一个虚拟机出现问题，它不会发生任何问题。别把我的整台机器都弄坏了。
每次我需要新的虚拟机时，我也不会从头开始。我有仅安装了操作系统的基础映像，以及操作系统 + Office 和操作系统 + Office + Visual Studio，但没有其他。这样，每当我需要新的虚拟机时，我只需制作最接近我需要的基础映像的副本，然后从那里开始。唯一的限制是基础映像无法加入域，但这对我来说不是什么大问题。
我鼓励您自己尝试一下。效果很好。
I don't know the specific answer to your question, but I am running Office 2010 and still working on Office 2007 add-in development.
My solution to this problem has been virtual machines. I don't do any development work on my laptop's primary OS. I don't even have Visual Studio installed there, but I am running Office 2010 and really like it so far.
For development I've got dozens of different VMs with various configurations of OS and Office version and other 3rd party software that I need to integrate with. I'm currently using Windows 7 and the new version of Windows Virtual PC, but I started this practice when I was using Windows XP and Virtual PC 2007.
One benefit of this is that if something goes wrong on one of my VMs, it doesn't bring down my whole machine.
I also don't start from scratch each time I need a new VM. I've got base images with only the OS installed, as well as OS + Office and OS + Office + Visual Studio, but nothing else. That way, whenever I need a new VM, I just make a copy of the base image that's closest to what I need and go from there. The only limitation is that the base images can't be joined to a domain, but that's not a big deal for me.
I would encourage you to try this yourself. It works great.