Virtual directory and application directory

It looks like the issue with my new pages not recognizing the existing web.config file is because I did not publish the entire solution - only the new pages that I created...at least, that is according to the previous developer. The previous developer always published the entire solution. The entire site uses one web.config file. I also noticed that after the clean, compile, and build, my .aspx.cs and aspx.designer.cs pages are still visible in the solution - it doesn't look like they actually compiled (?). I am researching this issue before I convert the new folder.

I just re-built, re-compiled, and republished my new pages. I got the same web.config error: Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customerrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customerrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customerrors mode="Off">



When I create a new web.config in the folder with my new files and set the customErrors mode to "Off" so I can see what line is erroring, it stops on the first line - which is what successfully compiled:
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 'RescueDogs.NewBreeds.PlacementStatusReport'.

Source Error:


Line 1: <%@ Page Title="" Language="C#" MasterPageFile="~/Site.Master" AutoEventWireup="true" CodeBehind="PlacementStatusReport.aspx.cs" Inherits="RescueDogs.NewBreeds.PlacementStatusReport." %>
Line 2: <%@ Register assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" namespace="Microsoft.Reporting.WebForms" tagprefix="rsweb" %>
Line 3: <asp:Content ID="Content1" ContentPlaceHolderID="HeadContent" runat="server">


Source File: /NewBreeds/PlacementStatusReport.aspx Line: 1


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1031

The first line is the same in all of the previous files - except for the name of the new report.

I am open to any suggestions on how I can resolve this issue...short of creating a new web.config file for my new files and then converting that new file to an application.



Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customerrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customerrors mode="RemoteOnly" defaultredirect="mycustompage.htm">

Yes, the namespace and class matched the Inherits attribute. I copied and pasted to be sure. The rogue period is a typo. What resolved my error was removing the Inherits from the .aspx. When I published the .aspx from VS 2013, the .cs and .designer.cs also published. In the pre-existing pages the other developer wrote, only the .aspx appear in the folders.

I'm thinking my build didn't actually compile the code behind into the library and that's why I got the error...the .aspx page didn't see the .cs in the .dll because it wasn't there to be inherited.