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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesModule/Packadge Manifest file - moduleName and foldernameModule/Packadge Manifest file - moduleName and foldername
Previous
 
Next
New Post
10/18/2011 10:51 AM
 
Hello, 
i'm fairly new to module creation and deployment, we are working with DNN5 Community and we have 2 test environments and a production IIS server with DNN5 Installed. 
I opened the sources of an already created Module in VS2010 and made some changes to it, added Settings and so on, I tested it works great on my test environment, I created the packadge with the wizard in Module Definitions, I changed all the fields I could (Version # and Friendly name) and created my zip file, which contains the .dnn manifest file.
I'm wondering about 2 variables in the manifest file which I would like to change but don't know the effect it may have.
- moduleName
- foldername
I checked this link and it doesn'T give me much info:
http://www.dotnetnuke.com/Resources/W...
what I want to know:
can i just change the "moduleName" and the "folderName" variables in the manifest file (add a 2 at the end for example) save it and deploy it on my Production server and when I install it it would have a different name and folder than the one that's already there?
I don't want to overwrite anything I just want another module and be able to put it on a test page on the prod. site and see if it's working fine, then deploy it on the actual page.

hope it's clear. 
 
New Post
10/18/2011 12:16 PM
 
You shouldn't change the ModuleName in the Manifest file.  That's how it's stored in the DB on your development database - and you can't (shouldn't) change it.  It will lead to problems later on if you further develop the module and have more releases.  You'll then have to ALWAYS be sure to modify the manifest file.  You'll just run into more trouble.

What you should do (after backing up your source files for the module) - simply delete the module from the extensions.  Then re-create it w/ the new Module Name you want.  Simply bringing over your module source code.

As to the folder name - you bring up a good point as I'm not sure what exactly that's for.  I'd like say it had something to do with where all the files are located - but the manifest file clearly shows each control with the full folder location (DesktopModules/MyCompany/MyModule/MyFile.ascx) to that control.  

I hope someone can further shed some light on that.


Andrew Walker

Learn to make your own beer and wine at homeIf you enjoy making your own beer and/or wine - be sure to check out http://www.ForemostBrewing.com
 
New Post
10/18/2011 1:22 PM
 
Hi 
thanks for the info, 
I actuallty changed both and all the paths in my manifest file for the module (added a 2 at the end) and It installed the module successfully, then when I added it to a test page the errors started pouring in... 
Most of them because of a webservice i had included in my module that had the same name.
I will restore the DNN original files from another test site and erase the Module and Reinstall it from the module zip file which I will create without changing any module name or short name.

what about version number what would that do?
 
New Post
10/18/2011 11:23 PM
 
The higher version will automaticlly overwrite the lower version had been installed ot the site when process install wizard.

NovaSoftware ---a professional outsourcing company in China .
* More than 6 years' offshore experience in DNN
* Successfully developed 30+ websites , 250+ DNN modules, 50+ sets of Skins/Containers.
* Demo Site:http://dotnetnuke.novasoftware.com/
 
New Post
10/19/2011 9:34 AM
 
Hi, 
thanks for that, I recreated the packadge with only the Version numer that's different.
I started with an old backup of our DNN site, then installed the zip packadge, and it updated the instances of that module on all pages.
so I guess there is no (easy?) way to rename a module then install it on a site not to overwrite my old one?

2nd issue: In my packadge I also had a webservice I created and I am a bit confused about that:
it had the same name as the old webservice, will the new deployment of my module overwrite that webservice as well?
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesModule/Packadge Manifest file - moduleName and foldernameModule/Packadge Manifest file - moduleName and foldername


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