Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Module Issue: Deployment with out sourceCustom Module Issue: Deployment with out source
Previous
 
Next
New Post
2/11/2009 10:48 AM
 

Hello all,

I am currently developing a C# custom module and in my edit control, where I have leveraged a custom built user ascx control within it. 

I use VS 2005 to publish my complied version and proceed to include the necessary dlls into the installation zip file (without source).

I install my zip file unto a test site and I receive the following exception message:

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: 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.

I have read several posts about this situation even a submitted bug issue which was withdrawn but of no help.

Is there any documentation that is available for me to read in order to work around this issue?

Thank you for your time

Eric

 
New Post
2/11/2009 8:20 PM
 

typically when you get app_global or global.asax errors it means that the asp.net cannot create an application as either something in the bin folder or else the app_code folder can't compile. If it's something in the bin folder it usually means that you forgot a dependancy e.g. your ascx may require a referenced assembly that's not in the bin folder. To diagnose this the best way is to create a solution, add the dotnetnuke site to it and add your custom module as a class library. Change the deploy path for the custom module to be the bin folder for the dotnetnuke site (make sure it's a debug build and the dotnetnuke site has debug=true in the web.config). You'll be able to debug the module now by setting breakpoints - and can even attach the debugger to step through the code.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Module Issue: Deployment with out sourceCustom Module Issue: Deployment with out source


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out