whitewater
New Member
My page has several dropdown lists that get populated with information via a seperate code page and it all worked great, however I refreashed the page out of curiosity and the data stopped get populated. I restarted IIS, tried debugging the code and it seems as if the codebehind page just isn't getting called anymore. <BR><BR>I keep recompliing the project to see it that helps but no avail. <BR><BR><BR>anyone experience a similar problem?I have not come across this. Have you tried making changes to both files so the cached compiled version will not be used?? Does the dll for the codebehind exist in the bin folder?It's not using a dll, just a code-behind page for now. I have not made changes to both and tested but I have made changes to either one and tested with the same results. The HTML page displays the current page, but it's as it the codebehind page isn't firing the class constructor or Page_Load event anymore.Can you post your page and the codebehind... are you sure the codebehind is not firing at all?yeah, it is not firing. I change the codebehind to "whatever.cs" and it still works.<BR><BR>my code:<BR>aspx page:<BR><%@ Page language="c#" Codebehind="test.aspx" AutoEventWireup="false" Inherits="testclass" %><BR><BR>.cs page<BR>public class testclass : System.Web.UI.Page<BR> {<BR>protected System.Web.UI.WebControls.DropDownList sltST;yeah, it is not firing. I change the codebehind to "whatever.cs" and it still works.<BR><BR>If I change the name of the class I get an error....I have deleted the dll in the bin directory/rebuilt but no dice. I just can't get the page to fireI removed AutoEventWireup="false" from the page directive and everything started working normally again....<BR><BR>Any idea what this directive does?AutoEventWireup - This should be false for VS.NET code-behind pages and user controls. Setting AutoEventWireup to false disables the automatic Page wireup of page events when a specially named method is found in the code (for example, Page_Load). VS.NET always creates the page event wireup explicitly in codeMy guess is that the pages were referencing a DLL and the reference only changed when I changed the directives....odd...