Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Define "support"?</p> <p>When a member is marked as Obsolete, it's still there, unchanged, with the same behavior, it just means that it <em>may</em> be removed at some point in the future - legacy applications that still use it <em>will</em> continue to run, but new applications <em>should not</em> use that member or feature.</p> <p>If you're referring to "customer support" - as in if you give Microsoft a phone call and cough up for the Developer Support fee, then yes, the man-at-the-other-end-of-the-telephone will help you and maybe provide a hotfix if you discover a bug or problem with the marked-as-obsolete feature. After the extended support period ends, then Microsoft will not provide personal-level support for that feature, or anything in the entire product (the assumption being that you'd have upgraded to 4.0 or 5.0 or whatever) by then. But if your program works fine, and Microsoft pledges runtime support in future versions of Windows (as it has for VB6 on Windows 8) then this is a non-issue. Also, Microsoft does not remove impersonal, online support (e.g. KB articles) so you can still rely on that. But 2020 is 7 years away, we'll be up to .NET 6.0 by then.</p> <p>But if you do upgrade to say, .NET 5.0 and see that the Obsolete'd feature has been removed, that you need to change your code accordingly. Also Obsolete'd items (generally) will not be removed in point-releases or service-packs (unless it was a majority security issue).</p> <p>Remember, writing desktop software is not the same thing as mainframe software - the platform <em>will</em> change, your applications <em>will</em> break, and you have to keep on running the treadmill. The best you can do is conform to the platform requirements and pray for forward-compatibility. (This is the reason so many Windows 9x games don't run on modern OSes: the developers couldn't spare the time to do things properly, which sucks).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

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