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

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...trouble creating a module package without source codetrouble creating a module package without source code
Previous
 
Next
New Post
10/5/2011 5:32 AM
 
Hi,

I have created my own module and I have to create a package to install it on other dotnetnuke sites.
I want to package without source code (and obviously with .dll files).

First time, I've created package under DNN 4.9 and then under DNN 5.x.
In each case I've then added *.dll  inside .zip file. I've added also reference to new .dll file inside .dnn file and then delete reference to source code files (publishing site I've created a .dll file for each .ascx page of module, so instead of "mycontrol.ascx" I have "App_Web_mycontrol.ascx.dll").
Troubles:
creating package with dnn 4.9 and installing it correctly, when I use it I receive this error: sourde code missing!
creating package with dnn 5.x and installing it correctly, I can't use it beacause of .dll files were not placed under bin directory!

I note that difference between packages created with dnn 4.9 and dnn 5.x are in the elements in .dnn file:
dnn 4.9: <dotnetnuke version="3.0" type="Module">
dnn 5.x:  <dotnetnuke type="Package" version="5.0">

So, how can I make a package without source code?

I'm frustrated,
thank you

Andrea
 
New Post
10/5/2011 10:16 PM
 
you need to include the ascx files - when you use WAP projects their code (from ascx.cs) is compiled into the name of whatever the assembly is . In your case you're not using WAP (as your files are app_web_*.dll) instead you're using WSP which is a dynamically compiled module (though there is a hack to use precompilation to force WSP to create dll's which can be included -see http://www.dotnetnuke.com/Resources/Blogs/EntryId/453/DotNetNuke-4-3-Starter-Kit-and-Item-Templates.aspx ). However if you want to hide source I recommend the WAP approach and use templates e.g. (you can view the video at http://www.dotnetnuke.com/Resources/Video-Library/Viewer/VideoId/107/Module-Development-Template-Installation.aspx and the wiki has comprehensive guidance on this - http://www.dotnetnuke.com/Resources/Wiki/Page/Module-Development.aspx)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...trouble creating a module package without source codetrouble creating a module package without source code


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