I have a module thats view control loads another UserControl declaratively. This works fine when running from source ala the new ASP.NET dynamic compilation model, but when precompiled and published one will receive

DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'App_global.asax, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. ---> System.Web.HttpParseException:

This is touched on in a previous thread here. So as you can see anyone who is loading a UserControl declaratively is experiencing this issue. According to cnurse in that thread:

DotNetNuke 4.x does NOT support the Publish Website menu option in VS2005 or VWD, as it does not support the "Precompiled option" available in .NET 2.  This is because of the way we do Localization.

This seems odd considering all the tutorials regarding precompiling modules under ASP.NET 2.0 use this methodology? Can any core team member or otherwise provide some clarification? I have never had an issue with precompiling via VS Publish, the key part here is the loading of the UserControl declaratively as it is the common thread that causes the exception noted above for compiled assembly deployment. Thanks in advance.

DNN does not support precompilation because the way we support localization, that's correct. The solution to this issue is to rename all DNN localization special folders (App_GlobalResources, App_LocalResources) to something different, but then another problem comes in: .NET substitutes constants in code with their real value at compilation time. So if we change the current value in code for those two items, it will break a lot of modules that used them.

I always use the new WAP  mode for my modules development and never found any issue in dinamically loading user controls. Maybe to would like to take a look at this option.

---

Vicenç Masanas
Banyoles, Girona - Spain