Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
As the Microsoft code base evolves, some methods and metadata elements become unnecessary. Microsoft marks these methods and metadata elements as deprecated.
- Methods are marked with the SysObsolete attribute. Typically, this attribute recommends an alternative to the method.
- For metadata elements, the IsObsolete property is set to Yes.
The deprecation works with both binaries and design time. The referencing code keeps working as expected, and no immediate action is required. During compilation, any references to deprecated artifacts are reported as compile warnings.
Cleanup of deprecated elements
After a period of at least 12 months, Microsoft might remove obsolete methods and metadata elements.
However, if telemetry shows that you still use any obsolete methods or metadata elements, Microsoft won't remove them. This approach reduces the risk of breaking changes.
Minimize your risk of being affected
To avoid being affected when Microsoft deprecates methods and metadata elements, follow these tips:
- Compile your code base at least every 12 months on top of the latest code base. If you receive any warnings because your code uses deprecated artifacts, address those warnings as soon as possible.
- Avoid new dependencies on deprecated artifacts. Microsoft might have removed the artifact because there's a time window between when releases and telemetry are available.
List of deprecated methods and metadata elements
For reference, download the Microsoft Excel file ObsoleteElementsPerVersion.xlsx to see the artifacts that each major release marks for deprecation.