How do you add a new directory to DNN upon skin install? Is through the reference in the manifest?
Yes, you can create a new directory through a manifest file. This applies to modules, skins - anything that uses a manifest file.
You will need to use the fileComponent in the manifest file, and specifically, the basePath element in order to specify where in the website your files will be installed. You can also install in relative paths.
See more here : http://www.dotnetnuke.com/Resources/Wiki/Page/Manifest-File-Component.aspx
Related
Is it possible to "install" a module just by pasting the file of the module and just paste it into the DesktopModules folder and have the modules working on the website?
If not, is there a way where I can export the whole module from one system and install it onto another system?
Have you tried creating a module package for this module? (when you click the edit pen for the extension, you should find a "Create package" button on the top right).
Take care to include the assembly/assemblies needed, and also the Sql Server scripts to install the module correctly (often found in the module folder under Providers/DataProvider/SqlDataProvider/*.SqlDataProvider). There might be other files in the module folder (images, css, etc), be sure to include them in the package, then try to create it. You will find the ZIP file under /install/Modules then, move it away from there somewhere on your local file system (otherwise the installer might try to install it with the next update). Then try to update the extension in a testing system, check if it works and you're done. If there are errors it might be that you are missing some files that have to be included. Check the error messages, and restart.
There used to be a way using the /Install/Module/ folder (put ZIP file there, then call /install/install.aspx?mode=installresources) If you are on an old version of DNN (7 and earlier?) you can still use this. But you've got a load of security issues that should drive you to upgrade.
I don't know of a good way to do this now. For security purposes DNN removes the Install resources after an upgrade.
IF you already have the module installed in both locations, you could copy the resources for the file from server to server (DLL in the BIN folder and the contents of the desktopmodules folder) assuming you don't have any MANIFEST file changes that need registered.
I am creating a custom extension for DNN using Christoc's DotNetNuke Module and Theme Development Template
I add folders to my extension project and i do a release build, once i install the extension on my site the folders are not there. These folders are part of the extension project. Do i need to add them as resource to the extension or something? because my JavaScript folder and CSS folder are there once installed and i created these folders manaully my self also
Thank You
You need to add the Folder, or the FILE TYPES in the folder to the BuildScripts within my project templates. Look at the ModulePackage.targets file.
Chris
I changed source of DotNetnuke (a little!) and I want to package an install version of my new DotNetNuke.
How Can I do this?
p.s: I know It's not recommended to change the source but I have no another option
(Telerik calendar do not support my date format and I have to replace it with another calendar !)
Thanks in advance
Answer depends on what you have changed, but the simplest way is to deliver patch that should be installed after normal dnn installation. For example, if you have only changed dll, you can ask to follow normal dnn setup instructions and finally relpace dll. If it's more than on file, you can review how dnn upgrade package is built. It follows same folder structure and places only changed files. So if you have couple of dlls changed in bin, the will be placed in bin folder, and if you have changed some ascx file it should be placed in same path by creating same folder hierarchy.
You can also create a package that can be installed to deploy your changes but for smaller set of files it will be complecated.
Let me know if you need more help.
You can package any change into a DNN install package by including the compiled files along with a DNN Manifest file. This can then be installed via the Extensions page. A manifest file is an Xml file which controls where the contents of an install zip are installed. You can make it as simple or as complicated as you need. You can also include xml merge statements to make changes to the web.config file upon install and uninstall. See the wiki for reference : http://www.dotnetnuke.com/Resources/Wiki/Page/Manifests.aspx
Incidentally, you may have been able to deliver your modified telerik source as a separate provider, and configure it via the web.config, thus saving you from modifying the source code. To do something like that, you would build your own module, and plug it in and replace the standard Telerik references.
Hi DotNetNuke experts :)
I want to make some changes in dnnfeedback source and I want to add module definition to site
in previous release of this module I used to go to "host-->extensions" and from action menu choose "create new module" and simply add the manifest and use it
But in latest module release the manifest extension was changed to .dnn6 and my DotNetNuke (version:6.1.3) doesn't show me anything to choose from.
I think this section of DotNetNuke Doesn't understand .dnn6 extension.
so how can I add definition of this module?
Thanks
if you wanna to change a source code just install the package and replace the DLL file with that one you've changed
You can simply use "Install Extension Wizard" instead of "Create new module" option and select the downloaded source package .zip of the Feedback module. It will install source files into DestkopModules/Feedback folder and you can make your changes there.
A little about .dnn6 manifest files can be found here.
I have folders inside a module which I developed and there are many files inside them.
How can I package the folders with files?
Should I archive the folders in a zip file? If so, how can I extract them again?
You have a few options.
Include a resources.zip file, that will be extracted for you upon installation, just be sure to include the resources.zip in your .dnn file list.
If you are using a DNN 5.x manifest, you could keep the folder structure within the module and just use the folder names items in the 5.x manifest.