Today marks the official announcement of VMware deprecating the vSphere C # client and officially taking the path towards the HTML5 client. This means that when new releases of vSphere are released, there will no longer include the C # client and only the HTML5 client will be used. Here's the official link to the VMware blog post on the subject Goodbye vSphere Client for Windows (C#) – Hello HTML5 - VMware vSphere Blog - VMware Blogs
This was discussed in a pre-news release with the vExpert community on Monday May 16th and there were mixed reactions to the news. It's no surprise since VMware has been hinting at this for quite some time now and that eventually this day would come. Some of the vExpert feedback included 3rd party plugin support and how to publicly make that information known (which included a feature request on the product interop matrix page as a possible solution), performance issues with things like importing multiple OVA files and having to use the C # client due to Web Client's inability to perform, and additional examples similar to a mass cluster exodus of VMs that could only be performed with the C # client due to emergency change related activity. These were just some of the examples discussed and added to the concerns with the announcement.
What does that mean?
Future releases of vSphere will only have the HTML5 client. If you haven't tried it yet, give it a test drive here vSphere HTML5 Web Client and see if it's the right time to move on.
Will I still have support for the existing C # client?
Current versions will still be available and continue to be supported with the supported versions of vSphere available.
Need to provide feedback? Hit the official VMware blog site link above and let them know how you feel or fill out a quick survey here Is it time to let it go?