Calling .Net Assemblies from PowerBuilder Classic Win32 via PowerShell
Recently someone asked me how they could get the output from PBDOM used from a PowerBuilder Classic Win32 application formatted with white space as PBDOM doesn't include it. I gave them a number of options, particularlyMSXML through OLE Automation or using a .Net class like XmlTextWriter. Normally if you were going to try to access a .Net assembly from a PowerBuilder Classic Win32 application, you would do it via a COM Callable Wrapper. However, for something this simple I thought there had to be a more lightweight way to accomplish it. One particular lighterweight way that occurred to be would be to have the application launch a Windows PowerShell script that would then use the .Net class in question. We're going to look at an example of how that's done.
The first thing we'll need is the PowerShell script to do the work. This is what I came up with (referenced as prettyprint.ps1 in the later code):
The script declares a couple of parameters (the input xml file and the output xml file). It then loads the System.Xml.Linq .Net assembly via reflection. Finally, we load the file and then write it back out again with white space. The last few lines are just for debugging from a command line prompt, as it displays a "Press any key to continue..." prompt before closing the PowerShell process window.
To test it through a batch file, I used this:
The assumption here is that the batch file, the PowerShell script and the input xml file are all in the same directory. I've got a pause statement in this script, so you actually get two "Press any key to continue..." prompts. If it works properly, that's all you should see. Otherwise you should see the error message from PowerShell or the batch file.
Once you know it's working, it's time to call it from PowerBuilder. I'm going to cheat a bit in the following example. I'm using the PowerScript Run function and have hard coded the location of the PowerShell executable. In actual usage, you might query the operating system for the location of the SystemRoot, or use the ShellExecute, ShellExecuteEx orCreateProcess Windows API functions to invoke the process rather than Run. Also note that the code assumes that the PowerShell script file is located in the same directory as the PowerBuilder Classic Win32 application.
In this case, the application prompts the user to select an XML file to process and then provide a name for the "pretty" version of the XML to output.
Without the second argument to Run, you will see the PowerShell process window open momentarily. If you were to continue to use the Run method, you can pass Minimized! as a second argument to that function to suppress the window. In addition, the ShellExecute, ShellExecuteEx and CreateProcess Windows API functions have options to suppress the PowerShell process window from displaying.