HI,
I have bult several modules now but I am having a really weird problem with one I am working on.
The site is 5.6.0 and newly built in VS2010 - I have had a fair bit of pratice moving sites around.
My module has an AJAX TabPanel with tabs and in one of them is embedded an IFrame (with a file upload control). it works fine in VS2010 but when I put it on the server (Server 2003 .NET 4 running in its own pool ) the module loads correctly, tabs etc all work but the IFrame shows a 404 error. I have checkednd triple checked references and paths and it works fine in VS2010 :/
IIS logs show nothing out f the ordinary I can see I can see the embedded page being requested but there appears to be no errors.
I have checked the application path and that is just "/" and the path to the aspx being called from the .ascx  is "DesktopModules/WA.AddRecord/FileUpload.aspx
I wonder if anyone has any ideas?
TIA Julian

please see my answer at http://www.dotnetnuke.com/Resources/Forums/tabid/795/forumid/203/threadid/401064/scope/posts/Default.aspx

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Thanks Andy for your input:

>If you copy the url path directly into a new browser, did you still get 404 error?
Yes

Can you make sure that you use Globals.ApplicationPath (API from DNN) to determine your local path?
Yes I did path is "/"

I have managed to get it working however . . .

The problem appears to be the module's folder name.

I used the recomended "MyCompany.ModuleName" format for the folder as I always do and so used "WA.AddRecord" for the module folder.
I noticed that none of the DNN modules used the "." so I used the animated .gif test to prove that if I changed my "Test" folder to "WA.Test" then I could no longer access the gif (weird).

So I then uninstalled the module, changed the module folder name from WA.AddRecord to WAAddrecord, adjusted the namespaces in the Settings and View pages, reinstalled the module by creating it from the controls and the problem is gone!

The site is DNN Community Edition version 05.06.00 (459) running under its own App Pool under .NET 4 on IIS6 on a Windows Server 2003 fully patched and which appears to be working properly in all other respects.

However I then tried the WA.Test in OTHER sites on the server and I get the same issue. Therefore it looks as though there is this is a server issue but I have no idea what! (I am going hunting however)