Obsolete the SOE

If you don't want to be forced to use an SOE, don't build desktop applications.

Secondly, don't build web applications that rely on anything that isn't a web standard. That includes anything that relies on a plugin, like Silverlight.

It occurs to me that if all enterprise applications were standards compliant web applications, the only thing an employee should ever need is an up to date browser. They shouldn't need an SOE. The IT setup process for a new employee should be:

  1. Give them a wad of cash to buy any machine they like
  2. Give them a login - ideally something that supports federation without actually needing to be joined to the network. OAuth or OpenID maybe?
  3. Give them the URL to your corporate portal
  4. Give them a network cable

If there's nothing to install on their system, there's nothing to be worried about when it comes to OS upgrades and messing with your precious SOE, since you won't have one. If the OS upgrade includes a new web browser, you shouldn't have a problem, since you used standards compliant HTML and CSS.

A picture of me

Welcome, my name is Paul Stovell. I live in Brisbane and work on Octopus Deploy, an automated deployment tool for .NET applications.

Prior to founding Octopus Deploy, I worked for an investment bank in London building WPF applications, and before that I worked for Readify, an Australian .NET consulting firm. I also worked on a number of open source projects and was an active user group presenter. I was a Microsoft MVP for WPF from 2006 to 2013.