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.0How to change built in module functionalityHow to change built in module functionality
Previous
 
Next
New Post
9/15/2006 10:04 AM
 
jbrinkman wrote

Sebastian -  The Source version of the module that is posted on SourceForge does not include the sourcecode.  We need to load the correct version on SourceForge.  I have posted a message to the core team forums to get the appropriate person to handle this (I am not sure who actually handles this specific task).

Joe,

I am not sure,  but I just downloaded Store_01.00.00_Source.zip from SF. This file has a file DNN_Store.resources inside. I renamed this to DNN_Store.resources.zip and found inside a large number of cs files. Are you sure, these is not the source of the Store module?


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/15/2006 10:19 AM
 

Sebastian - You are absolutely correct.  I completely forgot about this "feature".  Since I don't work with core modules much anymore, I forgot that we had a special way of packaging them (which clearly is confusing to some users and some dimwitted core team members  ).

The sad part is that these are packaged this way because of a mis-understanding about a feature that I implemented two years ago.  When we first added the "ResourceFile" node to the dnn manifest format, people thought that it meant you needed to name the file with a .resources extension.  This is clearly not the case, but that convention seems to have stuck (everywhere except in my brain).  Maybe we can get the convention changed in the future so that I cotinue getting older, it will be easier for me, and one or two new DNN users, to figure out.


Joe Brinkman
DNN Corp.
 
New Post
9/15/2006 10:33 AM
 

Joe,

thank you for your clarification. I have to confess, that I still have difficulties with details of the packaging process:

for installation packages, there is the option to add an resource file, that reliefs from the duty to list each sigle file in the .dnn config file, it is named "resources.zip". In source packages, there is a resource file called "DNN_modulename.resources". Do you tell me, that the name is not relevant at all and I can use a single .dnn file for both packages?


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/15/2006 11:21 AM
 

Thank very much all of you for replying this thread.I have download both the versions of store module 01.00.00 and 01.00.01 with source but no one contain the code behind file. it contain only .ascx, .ascx.resx,dll and some html files or script files but no .cs file. Can you guys plz alert user while they are downloading the source code.That this ver will intall only the framwork source code not the source code for the modules or make a readme file something like this.this is only a suggestion for the core team member so that new user don,t confuse.Anyway my email address is (rahimali.ali@gmail.com) can any one send me the module with source code. I alread email to  jbrinkman for the source code.once again i am very thankful to all of u who responsed this thread.

Regards rahim ali.

 
New Post
9/15/2006 11:33 AM
 

rahim ali

The result of our posts above:

  • you need either DNN3, VS 2003 and ASP 1.1 to modify the module or migrate the source to DNN4/ASP.Net 2.0
  • The source package of the store module DOES contain the source files! to get the files:
    • download and unpack the file Store_01.00.01_Source.zip
    • rename unpacked DNN_Store.resources to Store.zip and you will find the source files inside
  • The module installer in DNN3 should be able to do unpacking all files automatically, when installing the package using "upload module"

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to change built in module functionalityHow to change built in module functionality


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