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/
Related
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've installed XCode and MonoTouch and built a basic app.
I'm trying to integrate Flurry Analytics into my application. I signed up and downloaded the SDK but I don't know what to do with it. I think I need a binding library and I found this one on GitHub.
Should I clone that repository or is it already installed somewhere because I have MonoDevelop installed? Is there somewhere standard I should clone it to?
I then add a reference from my application to the FlurryAnalytics.dll. Do I need to do anything with the FlurryAnalytics SDK?
You only have to add a reference to FlurryAnalytics.dll in your project, no need to do anything with the SDK you downloaded.
But have in mind that the dll in that git repository might be somewhat out of date, in which case you should rebuild the dll (and in this case you do need the SDK). Here is what you need to do:
Find libFlurry.a in the SDK and put it in the repository's FlurryAnalytics/binding directory.
Open a terminal and navigate to the repository's FlurryAnalytics/binding directory.
Execute make.
This should build an updated FlurryAnalytics.dll.
I have a client with dnn website. I need to develop module for it. How I can start? I'm using Microsoft Visual Studio 2010 now (trial version). I cannot access source code, just make new module and install it. What is the best practice to start on the environment like this? Other question is if I using trial version of visual studio, is my module will expire too?
These materials, especially video tutorials, might be really helpful to you when getting started with DNN module development: http://www.dotnetnuke.com/Resources/Wiki/Page/Module-Development.aspx They cover every part from installing DNN module project templates to development and packaging of the custom DNN module.
To your second question, the answer is no, your module will not expire after VS2010 trial expires. Another option for you is to use free express editions of visual studio 2010, for this case Visual Web Developer 2010. You can download it here: http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-web-developer-express You will not be able to use source control directly from express edition, but still there is option to use SVN and a client like TortoiseSVN.
Purchase and read this book: Professional DotNetNuke Module Programming
Visit the download page of DotNetNuke.com
Download the Community Edition. Install it on your dev machine, get it working.
Hook the Desktop Modules folder and bin folder (at least) to your source control
At the download page above, install the Visual Studio Starter Kit
Restart Visual Studio 2010
Start up Visual Studio 2010, create a new compiled DNN module project, make sure its location is in the Desktop Modules folder of DNN
Implement some test code
Install the module on DNN (install by manifest)
Add the module to a DNN page. Test it.
Make updates to your DNN module. You only need to uninstall and reinstall the module if you add or remove files or change the database setup scripts.
Build a deployable version of your module. (You make a zip file or something. Just read the book. I always have to refer back for this step)
Practice installing the DNN module on another fresh DNN Community Installation.
Once you are satisfied that it is installing correctly, install the module on the live site (Do backups first, just in case)
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.