I just ‘finished’ developing a simple Windows Service using VB.Net targeting the Microsoft .Net Framework 1.1. Now I know what you are asking, why not target .Net Framework 2.0 or maybe even 3.0? Now even though I wanted to develop the service in C# and 2.0, well the simple reason is that the server where the service was going to run off, a Windows Server 2003 machine only had 1.1 and the owner was simply not willing to upgrade the 2.0 for fear that the upgrade may break some of the older applications developed for 1.1.
The client was unaware the the various frameworks do not overwrite or delete the previous installs, rather, they sit side by side thus allowing the older applications to run on the older framework yet allowing newer applications take advantage of the newer APIs and Assemblies
This raises an interesting question from a consultant’s perspective. On one hand, you are hired to make help create and implement changes to an organization’s built in processes, yet in reality through out the organization there are those that resist change for a myriad of reasons. How do you convince those people that change will not have an negative impact them, their work, their department, their organization etc when they were not involved in the change planning process from the beginning?