Hi and thanks for helping, I am trying to deploy a new home page. It works fine on my localhost with personal IIS but when I install the files to my discountASPnet site ( http://www.electronicmirror.com/) I get the following error: Server Error in '/' Application. Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Could not load type '_Default'. Source Error: Code: Line 1: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %> Line 2: <%@ register src="header.ascx" tagname="header" tagprefix="uc1" %> Line 3: Source File: E:\web\electronicm\htdocs\Default.aspx Line: 1 Version Information:Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407 Here is the generic _Default.aspx page : using System; using System.Data; using System.Configuration; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; public partial class EM_Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } } Gary <!-- [HttpException]: Could not load type '_Default'. at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase) at System.Web.UI.TemplateParser.ProcessMainDirective(IDictionary mainDirective) at System.Web.UI.TemplateControlParser.ProcessMainDirective(IDictionary mainDirective) at System.Web.UI.PageParser.ProcessMainDirective(IDictionary mainDirective) at System.Web.UI.TemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateParser.ParseStringInternal(String text) at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir) [HttpParseException]: Parser Error: Could not load type '_Default'. at System.Web.UI.TemplateParser.ParseString(String text, String virtualPath, String basePhysicalDir) at System.Web.UI.TemplateParser.ParseFile(String filename, String virtualPath) at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() at System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) at System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() at System.Web.UI.TemplateParser.GetParserCacheItem() at System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String virtualPath, String inputFile, HttpContext context) at System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context) at System.Web.UI.PageParser.GetCompiledPageInstanceInternal(String virtualPath, String inputFile, HttpContext context) at System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String path) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, String path, String pathTranslated, Boolean useAppConfig) at System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --><!-- This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->
Hi again, problem solved.My new homepage is in asp verion 2 while my account setting was for version 1.1. I changed that and now my page is running fine. Thanks for your attention. Gary
Hi again, The code behind file is the partial class, "public partial class _Default : System.Web.UI.Page ". The version I included above names itpartial class EM_Defaultwhich was an error. The deployed version is _Default. I don't know what you mean by Re-sync your files/folders as I ran it on a personal IIS server on my desktop where it ran fine. If it is a configuration or security setting problem I don't know what it might be? Gary