I'm not really sure if this qualifies as an actual issue. A naming conflict is being created because the script name and function within it are both called Get-vmotion.
If I use Install-Script the script name itself registers as a command. When I try Get-vMotion it executes the script itself and registers the function, but I can not get it to run the function.
I've hit this before where two modules (Hyper-V & PowerCLI) had the same command name, and I got around it by prefixing the module when I import it, or directly referencing the one I want- (vmware.powercli/Get-VM instead of Get-VM). I have not been able to use that method in this case because the script isn't a module.
I'm not really sure if this qualifies as an actual issue. A naming conflict is being created because the script name and function within it are both called Get-vmotion.
If I use
Install-Scriptthe script name itself registers as a command. When I tryGet-vMotionit executes the script itself and registers the function, but I can not get it to run the function.I've hit this before where two modules (Hyper-V & PowerCLI) had the same command name, and I got around it by prefixing the module when I import it, or directly referencing the one I want- (
vmware.powercli/Get-VMinstead ofGet-VM). I have not been able to use that method in this case because the script isn't a module.