Usually, the manuals of the applications come aplenty with sample code in Visual Basic. Converting the code from Visual Basic to Perl is a mostly mechanic task and hence I never found the need to read tutorials for automating Windows stuff beyond reading the manuals or the help files that come with the target applications.
If you are lucky and your target application includes a macro recorder that records into a Visual Basic program, you can even skip the "read the manual" part of finding out what functions to call and simply record the actions you want and then translate the generated Visual Basic code to Perl. Thanks to OLE, you can remotely use the exposed APIs of the applications, and at least Microsoft is very good at exposing good APIs for Microsoft Office. With the exception of Outlook.
If you're unlucky and your target application does not expose an OLE API, then you will have to use Win32::GuiTest to send (preferrably) keystrokes, window messages or mouse clicks (fragile) to the target application to automate it.
If you're looking into accessing the Windows API, there is only one resource I can recommend, the Microsoft Developer Network (MSDN), which has the (current) Windows API online.
|