Chris Hammondhttp://www.chrishammond.comRSS Feed for Chris Hammond120Packaging your DotNetNuke Module using NANThttps://www.chrishammond.com/blog/itemid/865/packaging-your-dotnetnuke-module-using-nantA few years back I was enlightened by Chris Paterra in the ways of using NANT scripts to aid in the packaging of DotNetNuke Modules. Using NANT to package your WAP (web application project) modules within Visual Studio 2005 is a snap, and can save you a LOT of time each time you have to come up with a new release. Using NANT scripts we are able to create the Private Assembly Installation ZIP file and Source files for Engage: Publish by running a single command from the Command line. With our Publish module this process takes about 23 seconds on average, for our smaller modules such as Engage: F3 the process takes less than 2-3 seconds. To get started with using NANT scripts in your own development environment you need to download the latest (0.85) release from SourceForge, you can visit the project page at http://sourceforge.net/projects/nant/ Once you've installed NANT on your machine (I install it on my C drive in a c:\nant\ folder) you'll need to add NANT to your system variables path so you can call it from the command line. To do this: Right click on My Computer and choose Properties Go to the Advanced Tab Find the System Variables section and Modify the Path variable Add your NANT folder (c:\nant\) to the path, separating entries with the semicolon (;) Save the settings. Now I'd recommend adding a .BUILD file to your DNN Module's project/solution. I've provided a sample build file on our Tutorial Page at www.engagemodules.com, you do have to login in order to access the file. The provided sample file is a good start for your project, by opening up the file in VS2k5 you'll see it is a XML document with some basic information about the product name and folder location. You'll want to find the references to Engage and EngageF3 in the BUILD file and replace them with the name of your module and business name. You can also play around with the include/exclude options in the Fileset node to add or remove certain types of files from your packages. You'll see the two sections in the build file that define which ZIP files to create, one section is called CreateBinZip and one is called CreateSrcZip. Once you have the BUILD file setup you'll want to check a few more files in your DNN project. In the .DNN File be sure to set your module version properly and include the SQLDATAPROVIDER files, as well as the necessary DLLs. In the AssemblyInfo.vb (.cs in our case. At Engage as we do 95% of our DNN module development in C#) be sure to setup your DLL information and version information. By setting the version number in the assemblyinfo and .dnn file you can get NANT to include the version number in the package's file name, allowing an easy way to handle upgrades from version to version for your modules. Once you have all of the files in the solution setup properly you can run the NANT script. To do that bring up a Command Prompt, change directories to your DNN/desktopmodules/ModuleName/ folder. At the command line type "nant" and watch the magic happen. If everything builds properly the script will create a Package folder in your Module's folder, inside of the Package folder you should find two newly created ZIP files, one labeled Install and one labeled Source.   Technorati Tags: ASP.NET, DotNetNuke, DotNetNuke Tips, Daily Tips, NANT, C#, VB.Net, Module Development, Engage Posted from...Tue, 10 Jul 2007 17:07:00 GMTda0daae1-c76c-4e04-9b95-881f708d1154Engage Publish 4.4.4 Releasedhttps://www.chrishammond.com/blog/itemid/981/engage-publish-444-releasedTonight we released the latest version of Engage Publish, 4.4.4 (12/9/2007). This release has a few minor bug fixes, a few UI improvements, and some enhanced features! Here's a brief overview of the changes for 4.4.4. Be sure to read about all of the changes in the Release Notes for 4.4.4. Corrected some globization issues with datesEnhanced Article's Version DescriptionCorrected issue with PrinterFriendly pageCorrected a globalization with Language urls Upgrade Instructions: Backup your database before performing ANY module installations or upgrades. Install the module as you would a new module from the Module Definitions page. The module should upgrade itself from there. If you have any installation problems be sure to post in our Forums on EngageModules.com Engage: Publish is the industry's leading Content Management Versioning and Workflow module for the DotNetNuke platform. The module is developed by the team at Engage Software, you can find out more information about the module on the Engage: Publish page at EngageModules.com. Posted from...Mon, 10 Dec 2007 01:04:00 GMTd252993f-bfc5-42c4-91af-a3f0a6090861Using SignalR with DotNetNuke Moduleshttps://www.chrishammond.com/blog/itemid/2624/using-signalr-with-dotnetnuke-modules<p>This post will provide you with a basic tutorial for utilizing SignalR with custom <a href="http://www.christoc.com/projects" target="_blank">DotNetNuke Modules</a>. If you want to bypass the blog post go check out the source on GitHub, you can <a href="https://github.com/ChrisHammond/DNN-SignalR" target="_blank">Fork my Repository</a>. The module created here will be very simple, if you want a full blown module with more features be sure to check out the open source <a href="http://www.christoc.com/dotnetnuke" target="_blank">DotNetNuke</a> Module <a href="http://signalrchat.codeplex.com" target="_blank">SignalRChat</a>, and see it in action at <a href="http://dnnCHAT.com/">http://dnnCHAT.com/</a> </p> <p>SignalR is an ASP.NET library for using websockets and long polling in your applications. Basically what this means, is that you can have your web pages (or apps) maintain an open connection with a webserver, passing data back and forth, without having to do standard posts and gets for the content and functions. SignalR is a free library that you can get from <a href="http://www.signalr.net">www.signalr.net</a> and you can DL from <a href="http://www.nuget.org">nuget.org</a> right into your Visual Studio projects.</p> Mon, 25 Mar 2013 01:58:47 GMT5f72e06f-1233-4b2a-a217-38fd1b334f24New DotNetNuke Module Development Templates V2.2https://www.chrishammond.com/blog/itemid/2628/new-dotnetnuke-module-development-templates-v22I have released version 2.2 of my open source DotNetNuke Module Development Templates. Version 2.2 is really just a minor update for the release, with a couple of fixes, one big, and the rest fairly small. Wed, 03 Apr 2013 23:55:51 GMT13d0e61d-5c61-44b1-876d-8d161e7d1b29Customizing the latest Module Dev Project Templateshttps://www.chrishammond.com/blog/itemid/2618/customizing-the-latest-module-dev-project-template<p>This blog post is no longer being maintained, <a href="http://www.christoc.com/tutorials/aid/3">visit the Christoc.com Tutorial for customizing the module development templates</a>.</p> <p><a href="http://www.chrishammond.com/blog/itemid/2616/using-the-new-module-development-templates-for-dot.aspx">With the 2.0 release of my module development project templates last week</a> I’ve had a few inquiries into how to customize the templates. You can download the templates from <a title="http://christoctemplate.codeplex.com/" href="http://christoctemplate.codeplex.com/">http://christoctemplate.codeplex.com/</a></p> <h2>Why Modify the Templates?</h2> <p>First, why might you want to modify the custom templates? The main reason is that these templates are defined using a specific namespace, <a href="http://www.dotnetnuke.com" target="_blank">DotNetNuke</a>.Modules.*, which is fine in most cases, but what if you want to use your own namespace? Well you have to create a project, then search/replace all instances of that namespace, while not removing any DNN references at the same time. Customizing the project templates will allow you to define your own company namespace, email address, website, and even copyright information, in the template so that you do not have to search/replace every time you create a new project.</p>Chris HammondMon, 28 Jan 2013 15:36:34 GMTd97308a2-c44e-42a0-8e01-2d3e057f9406Using the new Module Development Templates for DotNetNuke 7https://www.chrishammond.com/blog/itemid/2616/using-the-new-module-development-templates-for-dot<p><a href="http://www.chrishammond.com/Portals/0/PublishThumbnails/Windows-Live-Writer/Using-the-new-Module-Development-Templat_858B/image_6.png"><img style="display: inline; background-image: none; border-width: 0px; border-style: solid; float: right;" title="image" alt="image" class="dnnRight" src="http://www.chrishammond.com/Portals/0/PublishThumbnails/Windows-Live-Writer/Using-the-new-Module-Development-Templat_858B/image_thumb_2.png" width="214" height="79" data-ob="lightbox[ThisPost]" /></a>With the release of <a href="http://www.dotnetnuke.com" target="_blank">DotNetNuke</a> 7.0 (and now the more recent 7.0.2), it was time to update my <a href="http://christoctemplate.codeplex.com/" target="_blank">module development project templates</a>. If you have worked with my module development templates before, here are the major changes for this release. If you haven’t worked with them before please read this whole blog post as I discuss how to get up and running with the templates.</p>Chris HammondFri, 25 Jan 2013 12:56:11 GMT0b7127db-8bf7-4af6-8e1e-06fff9b663da