It’s been a while since my last blog. In the last couple of months, we have been very busy preparing some fixes to the XenApp PowerShell SDK. I’m happy to announce the immediate availability of Version 6.1.2 of the PowerShell SDK. Since we never really explained the differences with previous versions, here’s a recap:
- Version 6.0.0 is the version that shipped with XenApp 6.0. Yes, that’s correct: the SDK was there from launch day! We did not have a unified help file, start menu shortcuts, and complete help for the Group Policy Provider available in this version. But on a vanilla XenApp 6 deployment you can start Powershell, add the Citrix snap-ins, and start using the Powershell SDK without any further installation.
- Version 6.1.0 is the first version that was available for download. This release was primarily intended to help out administrators by providing more thorough and simpler-to-use help.
- Version 6.1.1 was released shortly after 6.1.0, and it fixed a bug that affected programmers. In 6.1.0 the Citrix.XenApp.Sdk assembly, which simplifies programmatic SDK usage, did not work as intended and did not match the documentation. This release did not affect administrators that use the cmdlets for scripting only.
- Version 6.1.2, released today, fixes a bug that prevented the Edgesight agent from working when the 6.1.x versions of the SDK are installed. It also helps programmers using the SDK, by enabling better cross-version portability of programs written and linked against the XenApp SDK. Now, programs that leverage the XenApp PowerShell SDK are forward-compatible so that, for example, programs built against version 6.0.0, 6.1.0, or 6.1.1 will work when installed on a system with SDK version 6.1.2 installed.
If you have downloaded the XenApp SDK in the past, I encourage you to update to the latest version. Those using the SDK as a programmer’s API are especially impacted by these updates.