What you are asking for here is GUI automation. This is not the target use case for PS.
So, there is no built-in cmdlet for this and no cmdlet or function called Write-Content. The closet you can get on your own is to use the old SendKeys option.
# Send output to Notepad and view it wihtout creating a file first.
# Start notepad
# Get a list of servics and put on the clipboard
Get-Service | Clip
# Put the clipboard content in the notepad instance
However, that is really not reliable, because different cpu, graphic cards and really mess with trying to use it consistently across platforms.
Been there, done that, and still do it for small localhost’s where I absolutely know how it is going to flow.
There are modules you can download and use to assist with GUI automation …
… and are 3rdP tools like AutoIT.
All that being said, you’ll still have the issue of working to figure out what window you are trying to hit, UI element positions, etc. That sort of thing requires C# and other API calls to make sure you can get to that stuff.
There are numerous discussions about this sort of effort all over the web, and the pain / failure / successes experienced along the way. Just do a search for ‘PowerShell SendKeys’ or ‘PowerShell GUI automation’ and you’ll see this right away.
Lastly, all this GUI stuff, where you are trying to deal with mouseclick events, mouseover events, mousehover events, etc., is really only possible for an application you have personally written, in most cases, unless the app providers exposed / gave you API info to do this.
Here is a SO discussion that highlights what I am saying here and should be of interest to you.
How i can send mouse click in powershell
Update per comment / request
Codeplex has been around for a long while, but is not longer getting any activity. Hence the archive stuff. All of the stuff on Codeplex has been copied / hosted to GitHub and the like locations.
Which module are you after to load?
Ideally, you want this in you user profile module location...
.. but you can put it in both.
Sometimes, I have module not autoload as expected, So, I just manually load them via profile configuration or in the script that will use the module.
Import-Module -Name ModuleName
Import-Module -Name C:\Users\YourUserName\Documents\WindowsPowerShell\Modules\ModuleName