Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I tend to agree with @Lior Kogan, in that upgrading for the sake of it is not something that you should be arguing with management about.</p> <p>In fact, there are good arguments for <em>not</em> upgrading:</p> <ul> <li>if you've got a stable platform, why introduce potential instability?</li> <li>if we upgrade this, will it force us to spend more money upgrading other things?</li> <li>will it mean we have to force our customers to upgrade as well?</li> </ul> <p>All these things are big negatives to a business, and make a good case for maintaining the status-quo.</p> <p>However, upgrades are necessary at some point. There are a lot of very frustrated web developers out there who are cursing businesses worldwide for taking the above aproach to Internet Explorer v6: While those businesses were arguably doing the right thing for some time, they've now passed the point where it is difficult to defend staying still. It may not be the case for you now, but eventually the same will hold true for a .NET upgrade.</p> <p>The argument here would be that the old version of the technology is obsolete:</p> <ul> <li>it is no longer supported by the vendor, particularly with security fixes.</li> <li>it is no longer sold by the vendor, making it hard to increase your number of users.</li> <li>other technologies that we use rely on the newer version.</li> <li>our customers are asking us for features that can only be delivered using the new version.</li> </ul> <p>If any one of those points holds true than you may have a good argument for an upgrade that will win over the management. If not, you may have to stick it out.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload