Real time scanning of historical file versions cannot be skipped


Consider the scenario where you are using the SharePoint Object Model (OM) to update the file stream of a document stored in a SharePoint document library. You notice that while you can skip the real-time scanning of the current version of the document, you cannot do so for historical versions.

More Information

This is an expected behavior at the time of creation of this article. Historical document versions are read-only from the SharePoint OM perspective and are managed internally by SharePoint.

Article ID: 2833712 - Last Review: Apr 23, 2013 - Revision: 1

Microsoft SharePoint Server 2010