Home/ Questions/Q 3697966
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T04:55:27+00:00

I recently ran into an issue where I used a property that was introduced

  • 0

I recently ran into an issue where I used a property that was introduced in the .NET Framework 2.0 SP1. This caused the code to fail completely on a pre-SP1 machine. Now I’m starting to wonder if there are any other hidden bugs like this waiting to pop-up. Is there a tool, or any way to scan an assembly and see if there are any methods/fields/properties/whatever that are dependent on a framework service pack? Maybe something like FxCop or Reflector could do this, but I’m not sure how to do this. Any help would be much appreciated.

Just for reference, the property that was introduced in 2.0 SP1 that I tried to use was the Font.OriginalName property.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’d recommend looking into FxCop for this. Krzysztof Cwalina at Microsoft wrote some rules that should help you. Scott Hanselman also has a list of changes from 2.0.50727.42 to 2.0.50727.1378 (which is where you’ll see your OriginalFontName property).

    As a side note, according to Microsoft’s documentation for OriginalFontName

    This API supports the .NET Framework infrastructure and is not intended to be used directly from your code.

    • 0