SDK Versions and Compatibility

When you upgrade from an older version of the vSphere Client SDK, you must consider whether your plug-ins will be compatible with the new vSphere Client.

You can refer to the following tables for more information about the compatibility of the plug-ins you developed with the different versions of the vSphere Client SDK.

Table 1. Compatibility Between the HTML Plug-In Created with a Specific Version of the SDK and the Different Web Client Applications
Version of the SDK That Is Used to Create the HTML Plug-In	vSphere Web Client 6.0	vSphere Web Client 6.5 and vSphere Client 6.5	vSphere Web Client 6.5 U2 and vSphere Client 6.5 U2	vSphere Web Client 6.7 and vSphere Client 6.7
version 6.0	Yes	Yes*	Yes*	Yes
version 6.5	No, if the plug-in uses APIs introduced in 6.5	Yes	Yes	Yes
version 6.5 U2	No, if the plug-in uses APIs introduced in 6.5 or 6.7	No, if the plug-in uses APIs introduced in 6.7 and 6.5 U2	Yes	Yes
version 6.7	No, if the plug-in uses APIs introduced in 6.5 or 6.7	No, if the plug-in uses APIs introduced in 6.7	Yes	Yes

Note: * If you have HTML-based plug-ins that are created with the vSphere Web Client SDK 6.0, you must follow the steps for upgrading your plug-in to ensure compatibility with the 6.5 versions of the vSphere Web Client and the vSphere Client.

Table 2. Compatibility Between JavaScript APIs and vSphere Client Versions
Version of the vSphere Client	vSphere 6.7/6.5 U2 JavaScript API	vSphere 6.0/6.5 Bridge API
version 6.0	No	Yes
version 6.5	No	Yes
version 6.5 U2	Yes	Yes
version 6.7	Yes	Yes

Note: The Bridge API is deprecated in the vSphere 6.7 release and the vSphere 6.5 U2 release. VMware will discontinue support for the Bridge API in a future vSphere Client release.