> ## Content Index
> Fetch the complete content index at: https://blog.tsd.digital/llms.txt
> Use this file to discover other available public pages before exploring further.

# Page name conflicts
- URL: https://blog.tsd.digital/page-name-conflicts/
- Published: 2006-09-21T20:46:33.000Z
- Updated: 2006-09-21T20:46:33.000Z
- Author: Tim Gaunt
- Tags: ASP.Net, .Net, #Import 2025-04-01 05:34

I know a fair few people have come across the error which, having a page called “Login.aspx” causes the error message “CS0108: 'ASP.login\_aspx.Profile' hides inherited member 'Login.Profile'. Use the new keyword if hiding was intended.” But I’ve found another when calling a page sitemap.aspx: “CS0108: 'ASP.sitemap\_aspx.Profile' hides inherited member 'SiteMap.Profile'. Use the new keyword if hiding was intended.” So just be careful not to name your pages the same as the controls.

If like me however you like to keep some sort of consistency in the page names across your sites, you can easily get around it by renaming the page’s partial class name to something which doesn’t conflict and then updating the page’s codebehind reference i.e. for sitemap.aspx:

public partial class\_pgSiteMap : System.Web.UI.Page {protected void Page\_Load(object sender, EventArgs e) { } }<%@PageLanguage="C#"AutoEventWireup="true"CodeFile="sitemap.aspx.cs"Inherits="\_pgSiteMap"Title="Site Map"%>