$application = New-Object -ComObject Visio.Application Store the returned application object in the $application variable: The application object is documented on MSDN and provides access to the Visio application. Because it is a COM object, you use the New-Object cmdlet with the –comobject parameter and specify the program ID of Visio.Application. When automating Microsoft Visio, the first thing you need to do is to create an instance of the application object. Though you cannot follow a Microsoft Word script and use it as a pattern to automate Microsoft Visio, if you are familiar with automating Microsoft Word the process involved with Microsoft Visio will not be completely new to you. One thing you will discover when automating Microsoft Visio is that the object model is similar to the object model for Microsoft Word or Microsoft Excel. First, I munch ANZAC Biscuits and listen to AC/DC.

Therefore, 50 degrees Fahrenheit and sunny is a perfect day to play around and write some cool Windows PowerShell scripts. The way I play golf, writing scripts is much more enjoyable. Golf can be an expensive hobby writing a script is free. If I played golf, it would be perfect weather for a nice 18 holes, but I do not play golf-I write scripts. It is a cool 50 degrees Fahrenheit outside (10 degrees Celsius) and sunny. I love Charlotte, North Carolina, in January. Is it even possible to automate Microsoft Visio? Is it possible? Is it too hard? What’s the deal? I have searched the Internet and have not come up with anything. I am going to assume that it can be done, because one of the great things about Microsoft Office is its customization and automation model. You have even written some stuff about automating Microsoft Office Outlook, but I have never seen anything about automating Microsoft Office Visio. You guys seem to have a lot of material about automating Microsoft Office Word and Microsoft Office Excel.

Microsoft visio viewer example