I'll also write some simple code for some of the tasks that the macro recorder either just can't record or doesn't record in an optimal way. Then I will use the latest version of VSTO included with Visual Studio 2008 to wrap this code into a deployable Word add-in. In this column you'll see how to use Word to capture some VBA code that solves a basic problem. But switching from VBA to VSTO doesn't have to be a case of throwing the baby out with the bath water rather, it can be just a natural way to extend how you are already developing solutions in Office. NET-targeted code rather than VBA-and doing so means using Visual Studio® Tools for Office (VSTO). The ability to call Web services is just one among a number of reasons for wanting to write. NET Framework CLR, on the other hand, understands these technologies quite well. As such, it's no wonder that making a Web service call isn't well handled in the context of Visual Basic for Applications. In the early days of VBA, XML hadn't yet been invented, the Internet was in its infancy, and the first HTML pages were just beginning to appear. However, even with all of the capabilities of Visual Basic® for Applications (VBA), there are some things it just doesn't do very well. And while writing a virus using a Word macro may be a dubious feat, it is a feat nonetheless. Macros have even demonstrated that they are functional enough to write viruses. For many years, the Office tools have featured macro recorders that weren't limited to simply replaying keystrokes but have been capable of writing code on the fly as well. It has been going on since the invention of macros, and there has been a full-fledged programming model within Microsoft® Office applications since the early 1990s.
Code download available at: OfficeSpace2008_05.exe(166 KB) Contentsĭocument automation isn't a new functionality by any means.
0 kommentar(er)
