I'm developing a DotNetNuke Module using the nonIIS method of module development. Is there any way to include a 3rd-party assembly in your module (when setting it up for deployment)?
I thought about adding it as a reference to the dotnetnuke_nonIIS website project as a whole, but that doesn't seem right considering it's a dependency of the module.
Whatever your local development environment may look like, you will most likely want to be able to deploy the module to a DNN site on its own.
To do that, you can create an installable module zip package - which consists of all of your module assets and a manifest file describing them so that DNN may process them and perform the appropriate actions (run scripts, deploy assemblies to the bin) upon installation.
Check out the DNN wiki for more information about packaging.
Related
I'm trying to configure the Swarm AS based on Thorntail 2.5.0.Final with a project-defaults.yml within a multi-module Gradle project. Unfortunately the configuration file doesn't get picked up.
Where do I have to put the project-defaults.yml file so it's registered by Thorntail?
Currently the situation looks like this:
I think the sub module resources folder is not correct, because this configuration file should configure the whole AS, right?
The file belongs to src/main/resources. It seems you already have one there -- are the two different?
If you have a multi-module project, generally there should be one module that builds the uberjar, and that module should have src/main/resources/project-defaults.yml.
I have already published dnn website. So Can I add my custom module in it?
I have purchased DNNGoxNews the module with source code from dnn store.
Now I want to modify some of the fields from some user control So How Can I achieve this.
I have already installed the module in my dnn website.But How can I modify the module.
Please point me the right direction.
Thank You
You will want to install this module in a development environment, which typically means a local copy of DNN
Follow this tutorial for how to setup your development environment.
Once that environment is setup, go to the HOST/EXTENSIONS page
Install the SOURCE package of the module you purchased
Open up the Project file, or Solution, in Visual Studio 2015
Make your changes, compile the module/changes
Repackage the module for deployment, if the source code doesn't do it for you automatically you can follow this tutorial.
Do we need the source code if we will primarily create (advanced) modules and occasionally modify the theme?
How does DNN get deployed from Teamcity / Octopus Deploy?
Your modules, and "skins" should be individual projects, and you should deploy those to production using Packaged ZIP files. That's the proper way to develop/deploy extensions for DNN
1.Yes, you should go to this url http://www.christoc.com/ to learn how to use a template to create a dnn module and create a skin as well.
Thanks to #ChrisHammond for your contribution to dnn community.
I am trying to create module within an existing multi-module maven project. This module will require Grunt, Bower, NPM, Angular JS, bootstrap among others. The output of this project (after the build is done) are static resources (fonts, js-files, application-js, application-css).
There is a separate Web module within the project that hosts the Web-Application portion of the Application.
I need to accomplish the following
Ensure that Maven can kick of the build of Grunt/Bower based UI Module.
Ensure that this module can be plugged in as a dependency for the Web Module.
So far, I have been able to figure out how to include a UI module as a dependency for a Web Project (via WEB-INF/lib/ui.jar...servlet 3.0 spec related).
Question:
What should the structure of the project be like to ensure that I don't copy unnecessary files into the JAR (like package.json or node_modules folder)?
Is there a way Maven can do an incremental build on such a project?
I am finding it hard to reconcile the two different project structures due to my own shortcomings I guess.
I was reading a DNN manual called 'DotNetNuke Module Developers Guide' for developing new modules from scratch.
The manual says to create a class library project and add reference to DotNetNuke project.
I do not find any such project in Community version source code for version 7.00.04. However, I can see DotNetNuke.Web and DotNetNuke.Web.WebClient projects but none that is called DotNetNuke.
There isn't a DNN project, but there is a DotNetNuke.dll, add a reference to that (the project I believe is DotNetNuke.Library)
I would also suggest taking a look at my Templates for DNN, they make doing module development easy http://christoctemplate.codeplex.com/