ASPX files are web pages that are generated by a server — in this case, SharePoint. They contain VBScript or C# code. ASPX files are written with Microsoft Visual Web Developer and are designed to run under the Microsoft.NET framework. Scripts within the page are processed on the web server, and the resulting HTML is sent to your browser.

With the exception of ASPX files stored in Libraries by users, ASPX files in SharePoint are usually system files. Any links that appear to be “contained” in these files are dynamically generated by the server at “run-time” when the file is called by your browser. The data that the ASPX file uses to generate and present these links is stored in the SharePoint database, not in the ASPX files themselves. For this reason, LinkFixer Advanced will not detect links in ASPX files in SharePoint (because no actual, static links exist there).

By default, LinkFixer Advanced skips all ASPX files in SharePoint, and all files located in the “forms”, “_catalogs”, “_cts” and “_private” system directories. You can over-ride these defaults by changing the “SharePointExcludeFolders” and “SharePointExcludeExtensions” settings in the “LinkFixer User Settings” file in the “\LinkFixer Advanced\Settings\” directory on your desktop.

In most cases, our users have found that it is not a good idea to modify system files in Sharepoint. We recommend that you maintain the default settings that skip SharePoint system files.

Similarly, data contained in SharePoint Lists is stored in the SharePoint database, and is currently not processed by LinkFixer Advanced.

Links contained in documents attached to SharePoint Lists are recognized and processed normally by LinkFixer Advanced.