Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

telerik -- supercharge your DNN websites
  Ads  
 


  Sponsors  

Meet Our Sponsors

WebSecureStores -- ASP.NET & DotNetNuke Hosting Solutions
FCKeditor Project
Salaro -- Skins and more
OnyakTech
CrystalTech Web Hosting™
Webhost4life, specialists in DNN hosting
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! ( Pr...  custom module version problem
Previous Previous
 
Next Next
New Post 4/23/2008 9:18 AM
User is offline steve conard
95 posts
10th Ranked


custom module version problem 
Modified By steve conard  on 4/23/2008 11:33:17 AM)

I have written another custom module using vs2008 framework 2.0.  I use 4.7.0 for dev site to test the module and the module compiles and runs without a problem.  I am trying to install (create) the module on a converted(upgraded) 4.5.1.  After install I consistently get the below error which is little help.  I have reference to dotnetnuke.dll in project that is set (default) to copy local.  I have a reference to microsoft.reportviewer.viewer that is set to copy local false.  Both dnn dev and test sites are on dev box and run other modules without issue.  Note that upgraded 4.5.1 site does not include the website directory as it was upgrade.  The file structure of the 4.7.0 site does.  I have tried many things in the last 24hrs.  Any assistance appreciated. 

Error: defdnndbreporter is currently unavailable.
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.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 4/23/2008 9:42 AM
User is offline Brian Dukes
477 posts
www.engagesoftware.com
8th Ranked


Re: custom module version problem 

The first thing that sticks out to me is that it sounds like you are compiling against 4.7.0 but trying to run against 4.5.1.  If you compile against 4.7.0, it will only run on 4.7.0 or higher.  Try referencing 4.5.1 when you compile (and probably turning off Copy Local so that it doesn't break your dev site) and see if that helps any.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
314.966.4000

The leading provider of DotNetNuke support, training and custom module development.
 
New Post 4/23/2008 10:02 AM
User is offline steve conard
95 posts
10th Ranked


Re: custom module version problem 
Modified By steve conard  on 4/23/2008 3:50:58 PM)

Removed reference to 4.7.0 dotnetnuke.dll.  Added 4.5.1 dotnetnuke.dll to new sub directory and created reference.  Set copy local to false.  Rebuild.  Placed new module dlls in the test 4.5.1 site.  Tried to open page with module.   Site times out/Module page never opens..

 
New Post 4/24/2008 6:08 AM
User is offline steve conard
95 posts
10th Ranked


Re: custom module version problem 

I have tried many things.  Any suggestions?

Thank You

 
New Post 4/24/2008 8:16 AM
User is offline Brian Dukes
477 posts
www.engagesoftware.com
8th Ranked


Re: custom module version problem 

 steve conard wrote

Removed reference to 4.7.0 dotnetnuke.dll.  Added 4.5.1 dotnetnuke.dll to new sub directory and created reference.  Set copy local to false.  Rebuild.  Placed new module dlls in the test 4.5.1 site.  Tried to open page with module.   Site times out/Module page never opens..

So, are you saying that it is a different issue now that you're compiling against 4.5.1?  You're seeing a time-out instead of the error message?  Are you no longer receiving any error messages?


Brian Dukes
Engage Software
St. Louis, MO
314.966.4000

The leading provider of DotNetNuke support, training and custom module development.
 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! ( Pr...  custom module version problem
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


XCESS expertise center b.v.
Custom made modules and complete solutions for the DNN framework. Maatwerk modules en complete webtoepassingen gebaseerd op het DNN framework.
www.xcess.nl
EMAS Pro
Strategic Enrollment Management Software for Higher Education Recruitment, Retention and Financial Aid
www.emaspro.com
Subzero Solutions
Dutch / English DotNetNuke consultancy services. Custom module development in any version. Complete application integration. Small business portal hosting. Your ideas our innovation - Your success our motivation. K.v.k Amsterdam: 34236342
www.subzero-solutions.net

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP