How does LinkFixer Advanced handle ASPX files and “Lists” in SharePoint?
Modified on: Tue, 17 Mar, 2026 at 10:59 AM
ASPX files are server-generated web pages used by SharePoint. They are typically created using Microsoft development tools and run on the .NET framework. These files may contain VBScript or C# code, which is processed on the server to generate HTML content that is delivered to the user’s browser.
In SharePoint, most ASPX files are system-level files, except for those explicitly stored in document libraries by users. Although links may appear within these pages, they are usually generated dynamically at runtime. The underlying data used to create these links resides in the SharePoint database rather than in the ASPX files themselves. As a result, LinkFixer Advanced does not detect or process links within ASPX files, since no static links are actually stored in them.
By default, LinkFixer Advanced excludes all ASPX files, as well as files located in system directories such as “forms”, “_catalogs”, “_cts”, and “_private.” These exclusions can be overridden by modifying the SharePointExcludeFolders and SharePointExcludeExtensions settings in the LinkFixer User Settings file, located in the \LinkFixer Advanced\Settings\ directory.
However, modifying SharePoint system files is generally not recommended. Maintaining the default exclusion settings helps preserve system stability and integrity.
Similarly, data stored in SharePoint Lists resides in the SharePoint database and is not processed by LinkFixer Advanced.
However, any documents attached to SharePoint Lists are processed normally, and links within those attachments are fully recognized and managed by LinkFixer Advanced.