I am going to start by saying that I am fairly new to the development of DNN modules so if I am going about something the wrong way please let me know the better way to go about this.

In short -  I have a custom module that consists of an ASCX file with a CodeFile. I can get it so that the ASCX file itself displays but none of the code in the CodeFile seems to run. For example I have a label on the ASCX file and I tried updating the text of the label in the Page Load event with no luck. When I debug the symbols seem to load (break point fills solid) but breakpoints are never hit. 

One thing to note is that I am actually trying to upgrade an existing module where we seem to have lost the code. A former coworker of mine "reverse engineered" the missing code which is now what I am working with. What I did was overwrite all of the old ASCX files and am updating the .vb CodeFiles for the new logic and the ASCX files to use the new .vb CodeFiles  and then  rebuilding the site in Visual Studio. This seems to have no effect on the behavior of the module. 

Most of the tutorials I have found on this have a very similar setup to what I am doing - ASCX files with .VB or .CS CodeFiles in the same folder and then additional code files in a subfolder of the App_Code folder - so I am not sure what it is I am doing differently that isn't working out for me.

Several questions come to mind

1. Am I missing any steps as far as how to properly update the back end code of an existing module?
2. Would it perhaps be better to delete this existing module altogether and treat this as a new module instead?
3. Am I perhaps missing something in the web.config file? (I did add a codeSubDirectories entry just in case...)

Figured it all out which it turns out was due to poor programming.

The error was caused by not properly implementing DotNetNuke.Entities.Modules.IActionable.ModuleActions on the ModuleActions() property of my user control. Though after fixing this my code did not run - more specifically just my page load event was not running.

Needless to say, turns out the programmer who reverse engineered the existing module did not wire up the event at all and thats why the code wasn't running. I'm kind of embarrassed I did not find it sooner but at least I figured it out. Now I just have to figure out what else he didn't reverse engineer very well....

Thank you!