If you are doing this with the webserver that is built into VS, you'll need to rebuild the application after making code changes.

The link to clear the cache is on the Host Settings page.

I'm using IIS for the web server. I'm not rebuiling the site each time. I open the pages on my local server and changing them in VS. I tried to clear the cache and that did nothing, so I guess it is something else.

Well, the only thing that I can think to suggest is to make sure that you save the changes to the file.

If you save the changes, and they still don't appear that would seem to be a very clear indication that the page is being cached somewhere. Check the module's caching parameter. Is there any chance that you are also using PageBlaster or a similar cache controller?

Not using any cache controller.

Here is the error message: Error: Success Tracker is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\inetpub\wwwroot\members\DesktopModules\SuccessTracker\SuccessTracker.ascx(238): error BC30456: 'Cal2_SelectionChanged' is not a member of 'ASP.desktopmodules_successtracker_successtracker_ascx'. ---> System.Web.HttpCompileException

Cal2_SelectedChanged was my deleted procedure from this morning. I have also rebooted my box and no change.

Module cache controller is set to 0.

It's hanging around somewhere, I just don't know where.

If you have rebooted that machine and the error persists, then I'd suggest that you didn't make all of the changes that you thought you made. Cached data won't last through that.

Is the code that references Cal2_SelectionChanged still present in SuccessTracker.ascx?

Found the problem. I did a search in the ascx file and found the problem. Originally I had double clicked the item to create the procedure. Then I just deleted it from the code behind file thinking since it was not there no problem, but it the even was still set in the ascx file, did not think that would matter, but it does.

Thanks for making me think about it again.

Darn it! I should have thought of that ...

I find it very useful to do development in a VS or VWD environment, and also to rebuild that application following code changes. If you do that, you'll catch things like this very quickly.

If you look at Michael Washington's http://www.adefwebserver.com/DotNetNukeHELP/ site, one of his tutorials shows you how to configure VS or VWD so that IIS is the default web server, too. If you are serious about developing modules for DotNetNuke, Washington's site should be like a second home to you.

It is very important to set cache timing for your applications. In DNN application/ site you can set cache in host setting page. To do that you need to login with the application/ site with host login and go to “Host Settings” page. Hit the “Advance Settings” tree and then click on “Performance Settings” link. Then you can find a dropdown where all the cache types are listed, name as below, No Caching: 0 Light Caching: 1 Moderate Caching: 3 Heavy Caching: 6 Below is the code I have picked from hostsetting.aspx file (admin\host\hostsettings.ascx). To set the cache time of your site you need to set the value with the cache name which will render in the host settings page under performance settings panel. <asp:dropdownlist runat="server" Width="150"> No Caching Light Caching Moderate aching Heavy Caching The value in dropdown ranges from 0 to 6. The code above takes the value set in the dropdown and multiplies it by 20 to determine the cache duration.