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...DNN Platform (o...DNN Platform (o...Packaging Custom Module without Source Code in 5.1.1Packaging Custom Module without Source Code in 5.1.1
Previous
 
Next
New Post
11/27/2009 5:46 AM
 

Sorry to be thick but which DNN Templates? I have the Module entirely inside its own folder on the DeskTopModules folder of the website within a VS2008 Project. I did a Publish Web Site and fished out the dlls for the Module in question.

 

 
New Post
11/27/2009 8:09 AM
 

Hi All.

More or less i'm having the same probs....

When "starting" the website from within VS i can use my module (with the source code of course), i can Publish (Compile) it, find my dlls with ugly names (e.g. App_Web_MyModule.ascx.dec30fbf.dll), placed them together with the ascx-files from the published website into a zip file, changed the settings in the DNN-File, can install it without any errors, but the module comes up with an error when placing it on a page.

Again, when building a zip-file with the source-codes my module is running, only the compiled ones are throwing errors.

Could this come from using the StartetKit.vsi for 5.2 and trying to install the compiled ones into a 5.1.4 site?

However, in my opinion, the creation and packaging under 4.9.x was easier then under 5. But maybe this comes from the lack of short (!) and consistent documentation.

 
New Post
11/27/2009 8:54 AM
 

When you are creating a dotnetnuke module (yes using the starter kit)  you can create the modules inside a website (which seems to be the aproach your using) or create them as another project which can be part of the global solution. When you create them as part of the website the files are created inside the deskotp modules but there's no way to generate an encapsulating dll for all the module's code (at least I've tried without succeding)

So when you want to use the module you use the "import manifest file" from the module extension module and then you pack it

But when you create it as another project inside the main solution you can actually create an encapsulation dll which you later copy to the binaries folder, create a folder for your module on the Desktop Module and copy al the files (js/css,ascx, ashx, and so on even the bin files) to the folder (except the source code and the debug files) then you can use the import manifest feature and finally you can procced to pack it


Jaime A. Jaramillo
Follow me on twitter
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Packaging Custom Module without Source Code in 5.1.1Packaging Custom Module without Source Code in 5.1.1


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