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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumCustomizing 04.04.03, issuesCustomizing 04.04.03, issues
Previous
 
Next
New Post
5/29/2008 7:30 AM
 

We have a DNN site we designed for a client a little while back and they came back with some basic changes they wanted to see to the Forum, one of which was to display Avatars in the members list, the version of the Forum we installed was 04.04.03 (not the source module) ..

So what I did was install DNN locally, same version as the one our client is using.. then I installed the Forum 04.04.03 source module and started tweaking it as they requested.

When I finished, I took the modified ascx file and the new compiled assembly dll and uploaded them to the live site, when I did that.. it did not work... instead I received the error you see below.

DotNetNuke.Services.Exceptions.ModuleLoadException: F:\inetpub\site-dev\DesktopModules\Forum\Forum_Container.ascx(3): error BC30451: Name 'ForumConfig' is not declared. ---> System.Web.HttpCompileException: F:\inetpub\site-dev\DesktopModules\Forum\Forum_Container.ascx(3): error BC30451: Name 'ForumConfig' is not declared. 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.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

The moment I put the original "DotNetNuke.Modules.Forum.dll" back in the bin folder, the forum loads normally .. 

I've not done any dotnet development in a few years, and I've never done any DNN development before so I don't doubt I'm doing something entirely wrong, all I know is that my modifications work locally ..

Any tips? or any more information needed?

 
New Post
5/29/2008 3:59 PM
 

Hi,

you have to create a new package with the dev. environment.  You find it in the Module Defination of the Host.  The Portal wich you will upgrade must have the same DNN Version as it was used for compiling or above.  Then install the new package over the Module Defination of the Portal. 

Other issue can be that the references to some DLL's are brocken in your dev. environment.  Please check the DotNetNuke.dll and Microsoft.ApplicationBlocks.Data.dll .

 

 
New Post
5/29/2008 4:57 PM
 

Ahhh I thought I had the same version in both envrionments but I don't.. the live site is .1 version behind my development envrionment..

I'm going to have at this again and I'll update you when I get finished, thank you!

 
New Post
5/29/2008 5:36 PM
 

Upgrade the live side .  I suggest to upgrade live sides with new DNN versions, it fixes some security risks. 

 
New Post
5/29/2008 6:43 PM
 

I will want to do that in a test area .. I'm not sure what is involved in upgrading so I want to mirror the site entirely and upgrade that so I know what I'm in for first :) but yes it's on my agenda .. next week in fact

At any rate... I installed the same version of DNN locally this time, installed the forum source, applied my code changes and compiled .. then all I did was upload the new ascx file as well as the DotNetNuke.Modules.Forum.dll file ... SUCCESS

Thank you for your help :)

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumCustomizing 04.04.03, issuesCustomizing 04.04.03, issues


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