Now that XenApp 6.5 is out and available to the public, it’s time to get the SDK into your hands! The XenApp 6.5 Powershell SDK is now available as a nuget package (from within Visual Studio) as well as located on our Developer Network. You can get nuget package system from http://www.nuget.org.
For more information on the NuGet/Citrix Packages see in the “Important Information” link below along with the Video tutorial.
What’s new in 6.5 SDK release
All the commands now support a -ComputerName parameter which indicates to the cmdlet to execute remotely. This means that the snap-in now can be installed anywhere and no additional configurations are needed in the client or server.
To accomplish this feature, a new WCF service (Citrix XenApp Commands Remoting) was introduced in XenApp, which essentialy implements all the business logic of the cmdlets. This logic is contained in a separate assembly, which in the case of server execution (when the commands are ran on the server) it is loaded in the same process where PowerShell is running.
Default Compute Name
In order to facilitate running existing scripts remotely without having to make significant changes, a default computer name can be set in the client machine. To do this a new set of cmdlets was introduced. When the default computer name is set, all the cmdlets will automatically remote to the server specified without having to explicitly use the -ComputerName parameter every time.
Since many cmdlets might be executing remotely, the calls to the back-end are minimized so that the remote execution performance will not degrade significantly when compared to local execution. One way to increase performance is using object Ids. Having the ID of the object minimizes the conversion calls that take place when operations are performed, for example, when deleting a batch of applications or folders. In order to minimize the changes to the existing public interface. The object names were overloaded with object id values. This means that anywhere where the cmdlets ask for a name, such as a server or an application name, the object ids can be passed instead. This feature is not necessarily intended to be used by the interactive user in the PowerShell console, but rather by developers that wish to write code with the SDK.
Nuget has become a great and efficient way for developers to get free libraries injected right into their .NET project without leaving the Visual Studio environment. Since its release, the NuGet package system is certainly gaining steam, currently there are currently 889 .NET packages and growing in NuGet, all available from right within Visual Studio, including 5 Citrix SDK’s.
So we are now at 1100+ SDK downloads and we want feedback! What are you building with our SDK’s? What are going to build with the 6.5 SDK? Share what you are building with the SDK’s, even if its an internal app and we’ll put it up on SDK central. Ping me on twitter, @johnmcbride or send me an email and we will showcase it on our SDK central site!
As always, send me your feedback. Share what you’re doing with us and lets help build the SDK community! You can ping me on twitter @johnmcbride or you can email me at john dot mcbride at citrix dot com and let me know!
One last thing, take the quick polls below and give us some feedback on the Citrix SDK’s and NuGet!
Citrix SDK’s/NuGet Video Tutorial
Quick video tutorial showing how to the use this NuGet to download some of the Citrix SDK’s
For more information on NuGet you can check out the following resources