I can imagine a scenario where Microsoft will create a security patch for some versions of .NET and not others. This might occur in occasions it's too expensive to regression test and back port all the changes.

Are there any examples of some security fixes created for one framework and not another?

This information would be used to access risk of legacy .NET applications that have not been migrated to the latest and most supported version of the .NET framework.

  • If I recall correctly, yes it possible that a vendor will decide to roll out a security fix for one version and delay for an older version. I don't know if this has happened specifically for .NET framework.
    – Majoris
    Jun 13, 2012 at 13:06

1 Answer 1


If you visit http://support.microsoft.com/lifecycle/search/default.aspx?sort=pn&alpha=.net+framework you'll see Microsoft's support lifecycle for the .NET framework.

As you can see, many of the older versions are no longer supported, so Microsoft do not promise they will issue security patches for them, and you should no longer use them.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .