Load Octopus.Client in powershell

mfrank · 1 May 2014 16:59

Just getting started with Octopus and would find it useful to load the client assembly into powershell for scripting. Having some trouble. Any advice?

Paul_Stovell · 5 May 2014 11:23

Hi,

Sure, here’s an example (the details are valid, you should actually be able to execute this and see machines):

gist.github.com

https://gist.github.com/PaulStovell/dccf2e7de64f4d18c36f

Script.ps1

# Don't forget to change the path below to your copy of Octopus.Client.dll
Add-Type -Path "C:\GitHub\OctopusDeploy\source\Octopus.Client\bin\Octopus.Client.dll"


$endpoint = new-object Octopus.Client.OctopusServerEndpoint "https://demo.octopusdeploy.com","API-RORM5DBGZMOSYGE7OSE5EZPQA"
$repository = new-object Octopus.Client.OctopusRepository $endpoint

$envId = $repository.Environments.FindByName("Production")
$machines = $repository.Environments.GetMachines($envId)

This file has been truncated. show original

Paul

mfrank · 5 May 2014 14:57

Thanks Paul. That’s what I tried originally but I get an error

Add-Type : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

I was thinking this was an issue with loading the dependent libraries that get pulled down with the client package. I pulled it down to a standalone directory using nuget.exe. I tried dumping everything together in the same directory but that didn’t seem to help. If I load everything from nuget in visual studio everything works properly. Any suggestions? Thanks for your help. So far we’re really loving Octopus. You probably have a new customer coming on board shortly.

mfrank · 5 May 2014 15:18

Yeah, dug into the exception and it looks like it’s throwing when it’s trying to find the newtonsoft.json assembly. I’ll try loading that first and see what I get.

mfrank · 5 May 2014 15:58

I believe this is the issue. If I load the assembly using [reflection.assembly]::loadfile() I get

Assembly : Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed

The exception being thrown is looking for this

File name: ‘Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed’

Is this an incorrect reference in the Octopus.Client package? Is my powershell being weird? Thanks again

mfrank · 5 May 2014 16:32

ok I loaded Newtonsoft.Json.4.5.11 package and then loaded that into PS first and now I am good to go. I talked to a real developer and I guess my visual studio project works because nuget automatically binds to the down level versions.

Nicholas_Blumhardt · 7 May 2014 22:34

Thanks for the follow-up; unfortunately a bit of a pain point when working outside of VS these days. Glad it is sorted out!

dalmiro_granias_notStaff · 23 July 2014 03:18

Loading Newtonsoft.Json.dll from Newtonsoft.Json.X package worked for me.

For the lazy fellas:

Add-Type -Path ".\Newtonsoft.Json.dll"
Add-Type -Path “.\Octopus.Client.dll”