What's new in the XenServer SDK

The XenServer SDK for PowerShell 7 is now built against .NET 10 and requires PowerShell 7.6 or later. The module doesn't load in earlier versions of PowerShell 7. The XenServer SDK for PowerShell 5.1 still requires Windows PowerShell 5.1.

Get-Help now provides full help for every cmdlet in both PowerShell modules: a synopsis, a description, a description of each parameter, and examples. The same content is available online in the PowerShell cmdlet reference.

The cmdlets now send an optional parameter to the host only if you specify it. Previously, when a later version of the API added an optional parameter to a call, the cmdlets always sent it, so the call failed against hosts running earlier versions that don't support the parameter. This fix affects actions of the Invoke-XenHost, Invoke-XenNetwork, Invoke-XenPIF, Invoke-XenPool, Invoke-XenSR, Invoke-XenVDI, and Invoke-XenVM cmdlets. For example, Invoke-XenHost -XenAction Disable now works against all XenServer 8.4 hosts, including hosts with older updates that don't support the -AutoEnable parameter.

The Go SDK now uses int64 for all XenAPI integer values, instead of int. Previously, integer values above 2147483647, such as memory and disk sizes, were reported incorrectly in 32-bit builds. If your code assigns these values to int variables, update it to use int64.

The Go SDK now requires Go 1.27.1 or later.

The Java SDK now depends on Apache HttpClient 5.6.4 and Jackson Databind 2.22.4, which fix security vulnerabilities. If your project declares these dependencies itself, update them to these versions or later.