Hello, I hope someone can help with this one.  It really has me scratching my head.  I have written a module that runs perfectly on my development machine and also on a production server.  Both of those machines are running 04.09.02.  When I try to install the Private Assembly version of my module on 04.09.01 I get the following error:

DotNetNuke.Services.Exceptions.ModuleLoadException: e:\hosting\member\comsite02\dnn\DesktopModules\csClassifieds\Classifieds.ascx(9): error BC30456: 'Page' is not a member of 'ASP.desktopmodules_csclassifieds_classifieds_ascx'. ---> System.Web.HttpCompileException: e:\hosting\member\comsite02\dnn\DesktopModules\csClassifieds\Classifieds.ascx(9): error BC30456: 'Page' is not a member of 'ASP.desktopmodules_csclassifieds_classifieds_ascx'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

The line it is erroring out on is simply:  If not page.isPostback then

Does anyone know of any reason why this may occur?  I am wondering if it has something to do with the compiled DLL files referencing something in the DNN build that changes between versions??  But I am just grasping at straws...

Well, I believe by default everything within the ME object is always in scope anyway.  But, I tried your solution and it did not help.  Just to narrow things down a bit, I created only one reference to the page object:

Dim oPage As Web.UI.Page = Me.Page

This still throws the error.  Maybe it has to do with the way my development machine is setup?  I followed the instructions in Michael Washington's PDF on DotNetNuke Module development.  So, I have the Install version of DNN installed.  I open the DNN website into VS 2008.  Then to create a new module, I right click the project and select Add New Item and choose DotNetNuke Dyanmic Module from the templates.  So, I don't have a seperate project for my module but rather it's part of the website project.  Then to distribute it, I am publishing the site and copying the necessary DLL files into my install zip.  Could this cause my module to be dependant on a specific version of the DotNetNuke.dll or something like that?

Please help, I have no idea where to even look for the answer to this issue.

Okay, so my suspicions were right.  It's a BAD idea to create your module by "Open Web Site" in visual studio, and then begin creating the module files in the website.  Even though you can publish the site, copy all the dll files from the publish folder and create a distributable module (as per Michael Washingtons instructions).  DONT DO IT!

Instead, download the source for the most recent version of DNN and the Starter Kit.  Then, open the VS Solution file from the source, and Add a new project to the solution.  The project will be the DotNetNuke Compiled Module template that gets installed by the starter kit.  Once I did that, now I have references in my project to the DNN dll files and I can specify Specific Version = False.

I am posting this just in case it may be helpful to someone else down the line.