Today we will learn How to Automate the Packaging of your DNN Module, let me to show you step by step :

• Delete all source code and start over from scratch with my templates installed.
• Open your project in Visual Studio
• Install the MSBuildTasks project from Nuget:

   PM> Install-Package MSBuildTasks

• Create a BuildScripts folder in your project
• Add two files (source for each here)
• ModulePackage.targets
• MSBuild.Community.Tasks.Targets
• Right click on the project in Visual Studio Solution Explorer and choose “Unload Project”
• Save changes if prompted
• Right click on the unloaded project and choose the Edit option
• At the bottom of the file, before the </Project> section add

        <PropertyGroup>
          <Extension>zip</Extension>
          <DNNFileName>CHANGEME.dnn</DNNFileName>
          <PackageName>CHANGEME</PackageName>
          <MSBuildCommunityTasksPath>$(SolutionDir)\Build</MSBuildCommunityTasksPath>
        </PropertyGroup>
        <Import Project="BuildScripts\ModulePackage.Targets" />
        <Target Name="AfterBuild" DependsOnTargets="PackageModule">
        </Target>
        <Import Project="$(SolutionDir)\.nuget\nuget.targets" />

• Change the “CHANGEME” text to match the name of your .DNN file and the name of the ZIP file that you want the package created as.
• Save the Project changes.
• Right click on the project in Solution Explorer and choose Reload Project.
• Switch into Release mode in Visual Studio and do a Build of your project.

This should create two files, ModuleName_Version#_Install.zip and ModuleName_Version#_Source.zip.
What I typically do then is install the module to a test DNN install to make sure that everything is working correctly. You’ll want to make sure that the ZIP files created contain all the right files, and they get installed correctly, so a test installation is the best way to go through that process.
If something fails, try to track it down, then do another Build in Release mode, rinse and repeat the installation process in your test install until you get everything working properly.

Now going forward, after you do a release, you go into your AssemblyInfo file, change your version number there, and into your .DNN File and change your Version number there. Next time you build in Release mode the module will create a new VERSION number ZIP file, leaving your last version builds there as well.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.