

Now, the thing I didn’t mention up to this point is that this application requires XML Core Services 4.0 with Service Pack 2. In these financially unstable times, for many organizations options 2 and 3 are not feasible either, so you’re faced with making the application run.

This is a critical business application, so the option to stop using it cannot be considered. Migrate to another (supported) application.Upgrade the application to a newer (supported) version.The company making the software has since gone bust or your organization didn’t have support, but the bottom line is you’re faced with three choices: Great! Now, also consider your business has bought this particular application a few years back. It features legacy functionality, unsupported software and security holes the size of Jupiter.Ĭonsider a critical business application, that works with XML. If you want to know how painful, keep on reading this blogpost. Legacy software is painful from a security point of view. Security and practicality often clash, especially with legacy software in the mix.
