I used the code sample in the linked article and got further. I was able to create the object but not open the connection. Said TNS could not resolve the connect identifier, even though both ORACLE_HOME and TNS_ADMIN are correctly set and the tnsnames file has the correct entries (also used by other connection types (e.g. Microsoft Oracle connector in SSIS) that work OK)
Any help would be great but I think this is an oracle question
Oracle is a pain. Luckily, I have not had to deal with it in a couple years. The below discusses the TNSName.ORA and other items to successfully connect:
As far as the assembly question, after the dll is loaded and the assemblies are available, you typically are creating a New-Object or referencing it with an accelerator (e.g. [myobject]::mymethod). I believe the -AssemblyName parameter is load a specific assembly from within a dll. This is not my strong suite, it’s not often that I’ve had to rely on loading a DLL to something in Powershell, especially as it’s become much more main stream with the community developing module wrappers to take the guesswork out of things like this.