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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Still struggling to package a simple module for 5.0?Still struggling to package a simple module for 5.0?
Previous
 
Next
New Post
1/9/2009 3:00 PM
 

please make sure you haven't zipped up the directory as well, it's easy to accidentally zip up the folder and not realise - the installer unpacks the folder, and then can't find the files

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/9/2009 3:16 PM
 

Also, if there's a way to get the packaged file to me, I can try install it to see if it works for me.

tb

 
New Post
1/9/2009 10:22 PM
 

Ah Cathal

That was the hint I needed. I was using IZARC and adding to the ModuleName.zip, not to Archive. This meant that all the files were in a folder named ModuleName nested inside the unzipped file. This was not a problem in 4.9 but obviously is in 5.0. Also I have placed the the dlls in a bin folder and the resx files in a app_localresources folder.

Now if we had a wiki I could record this for others.

Thank you and tb very much

Kind regards

Geoffrey


Geoffrey Morton-Haworth www.yalaworld.net
 
New Post
7/2/2010 6:55 PM
 
FYI I ran into to the same problem (Version string is too long or too short) and this post helped quite a bit.  In my case the 5.2.3 Create Package wizard added an extra/nonexistent file to the list for export into the package.  I simply removed the extra file and then the wizard ran correctly.

Before:
01.00.00.SqlDataProvider
HomeFeature.SqlDataProvider  <--- Removed this one 
Uninstall.SqlDataProvider
App_LocalResources\Settings.ascx.resx
App_LocalResources\ViewHomeFeature.ascx.resx
HomeFeature.dnn
web.config
Documentation\Documentation.css
Documentation\Documentation.html
Documentation\logo.gif
Settings.ascx
ViewHomeFeature.ascx

After:
01.00.00.SqlDataProvider
Uninstall.SqlDataProvider
App_LocalResources\Settings.ascx.resx
App_LocalResources\ViewHomeFeature.ascx.resx
HomeFeature.dnn
web.config
Documentation\Documentation.css
Documentation\Documentation.html
Documentation\logo.gif
Settings.ascx
ViewHomeFeature.ascx


-something clever or funny.
 
New Post
7/2/2010 7:14 PM
 
OK. Just gut checked my last post and DNN was correct in that the HomeFeature.SQLDataProvider file was in the file system.  It was a file created by the DNN Module VSTemplate.  The Create Package tool did make a mistake however in that it set the version tag of the that node to "HomeFeature" instead of "1.0.0.0".  After I changed the version I was able to leave the file in the package and everything was fine.

Old
<script type="Install">
<name>HomeFeature.SqlDataProvider</name>
<version>HomeFeature</version>
</script>

New
<script type="Install">
<name>HomeFeature.SqlDataProvider</name>
<version>1.0.0</version>
</script>

-something clever or funny.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Still struggling to package a simple module for 5.0?Still struggling to package a simple module for 5.0?


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