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 ForumsEventsEventsEvents Source and VWD2005Events Source and VWD2005
Previous
 
Next
New Post
10/2/2006 4:23 PM
 
i'm trying to extend the event module following your example, but i'm getting problems with DotNetNuke.Events.WebControls
if i put the dll in the bin folder, the module works but when i go to the settings this error show:
Error: Module is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.Modules.Events.EventController.UpgradeEvents(Int32 ModuleID) at DotNetNuke.Modules.Events.Settings.LoadSettings() at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

and if i put the files that came in the source code in the folder controls/DotNetNuke.Events.WebControls
under the folder app_Code, this error show when i see the module:
Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.Web.HttpParseException: Could not load file or assembly 'DotNetNuke.Events.WebControls' or one of its dependencies. El sistema no puede hallar el archivo especificado. ---> System.Exception: Could not load file or assembly 'DotNetNuke.Events.WebControls' or one of its dependencies. El sistema no puede hallar el archivo especificado. ---> System.IO.FileNotFoundException: Could not load file or assembly 'DotNetNuke.Events.WebControls' or one of its dependencies. El sistema no puede hallar el archivo especificado.

i am missing some files on DotNetNuke.Events.WebControls??

any help??

thanks,
Sebastian
 
New Post
10/3/2006 10:50 AM
 
For all you people who are trying to convert the Events module source to DNN4 go to the downloads page and look for the Module Upgrade Wizard.

I haven't tried it myself but the manual indicates that it automatically does a lot of the stuff that I had to do manually when I converted the module by hand.

Please let us know how it works.
 
New Post
10/17/2006 5:26 PM
 

One step I think was left out.  When and what steps are necessary for unzipping the source zip?

Thanks in advance.

 
New Post
10/18/2006 8:47 AM
 
When you install the source version into DNN 3.X the files will be automatically unzipped and placed in in folders beneath the main DNN folder.
 
New Post
10/20/2006 2:40 PM
 
I have been able to get all my conversion errors taken care of. Let me detail out what I did (thanks to earlier posts in this thread - they helped shed a lot of light for me):

First things first, you want to take all the .vb and .cs files (NOT ascx.vb or aspx.vb, ONLY .vb and .cs) out of the source (NOT install) Events project, and put them into the app_code directory in your web project (a working dnn 4.2.5 site). Create an Events subdirectory, and an EventsWebControls subdirectory. You want two because one is written in C# and the other in VB, you cannot mix the two. These files are:
DataProvider.vb, EventBase.vb, EventController.vb, EventInfo.vb, SqlDataProvider.vb, AssemblyInfo.vb, EventNotification.vb
and
AssemblyInfo.cs, ColorCollection.cs, ColorItemHelper.cs, ColorUtility.cs, DNNCalendar.cs, DNNColorDropDown.cs, DNNColorDropDownBuilder.cs, DNNColorDropDownDesigner.cs, DNNColorDropDownEventArgs.cs, DNNColorDropDownException.cs, DotNetNuke.Events.WebControls.xml, Enums.cs

Now you have to modify your web.config file to have these two extra codeSubdirecties - you'll find one already in there, so just copy, paste, and modify to have the two new subdirectories

I followed the instructions found in the Module Upgrade Wizard. I manually did the find and replace instead of using the wizard.

After being done with these instructions, I fixed a warning about an obselete class: simply copy the obselete attribute syntax from the base class and insert it over the DotNetNuke class declaration that VS2005 is complaining about.

There is a page ( I forget which one, just look in your build warnings ) that complains about using the old AppSettings syntax. Fix to be .NET 2.0 compliant

One thing that the Module Upgrade Wizard does not mention is the need to delete the AssemblyName="DotNetNuke.Events.WebControls" out of the @Register syntax found at the top of your ascx pages (this is IF you are using the app_code directory and not pre-compiled dlls). If you do not delete the assembly reference, then the code in your App_Code directory will not be used, it will still be looking to the bin folder for the assemblies.

Once you do all that, you will need to make some changes to the code.  I have posted here: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/mid/2108/threadid/19225/threadpage/2/scope/posts/Default.aspx#81131 instructions on how to do that.

Feel free to send me an email if you encounter errors or omissions here, I may have forgotten a step or something - but I think i've gotten it all...

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsEventsEventsEvents Source and VWD2005Events Source and VWD2005


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