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.0Installation of Custom Module IssueInstallation of Custom Module Issue
Previous
 
Next
New Post
12/23/2008 11:34 AM
 

I've got a custom module that compiles fine in the test environment, and I can manually setup the Mod Def in that environment and add a module instance.  When I transfer the ascx (single control) the DesktopModules>[ModuleName] of another DNN instance, and put the dlls into the website bin and setup the module definition and add the new module to a page, I get the error below.  Is there any way to get a handle on what these errors are???

DotNetNuke.Services.Exceptions.ModuleLoadException: vbc : (0): error BC30041: Maximum number of errors has been exceeded. ---> System.Web.HttpCompileException: vbc : (0): error BC30041: Maximum number of errors has been exceeded. at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() 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.Compilation.BuildManager.GetVPathBuildResult(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 ---

 
New Post
12/23/2008 12:09 PM
 

you might need to validate the error list in Visual Studio, obviously there are more than 100 (might be caused by a single missing reference or sth like this)


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/23/2008 12:19 PM
 

Sebastian, how do I go about validating the error list in VS?  It is occuring at runtime when the module is loaded.  I obviously already have a runtime source of DNN, but am not sure how to debug this one!  Thanks in advance.

 
New Post
12/23/2008 1:11 PM
 

Boy, I am more confused than ever.   Here are the steps I just took:

1) Downloaded a "new" source DNN (v4.8x is what all of them are), and put it on a server (IIS 6) and configured it.  I added the module project in the Desktop Modules and made sure that the dlls were in the DNN bin.  Then I added the module def for my (relatively simple by-the-way) new module.

2) I then took the resulting who DNN directory(s) and DB and copied them to my development machine (IIS 7 / Vista in case that makes a difference).  When I first added a module instance on both the server and the dev machine, they both gave the "too many errors" error.  I then opened up the DNN instance on my dev machine and compiled the WAP Project ONLY.  The dev machine custom module proceeded to work fine without any other changes!

I am pulling my hair out on this one as I see no difference between the 2!!!  Anybody have ANY clue or how I can fix this or at least diagnose?

 
New Post
12/24/2008 11:45 AM
 

To make sure the is not at all related to Vista/IIS 7, I've moved the development stuff to an XP box and configured.  I've got the same error in the DNN module load so I set a breakpoint on InjectModule (what appears to be the base of the exception - see above stack trace) in the DNN Library and it never gets hit.  Does anyone have any ideas on how I can work through this?

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Installation of Custom Module IssueInstallation of Custom Module Issue


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