This is a single that threw me for a long time, nevertheless the remedy is actually quite simple. Easy sufficient that i really don't understand why there is not much more documentation on it.

Here’s the scenario: You've got a module with two, or maybe more, achievable interfaces depending on the web page the module is additional to. The view handle features a blank important area and you cannot have copy crucial fields, blank or in any other case. How can you power the non-blank module control to point out around the page with out further coding?

The answer: make use of the module definitions.

Here’s how.

A number of assumptions very first:

You’ve developed a custom made DotNetNuke module.
You have at the very least two module controls in that module.
You've got a DotNetNuke set up to check on as well as the custom module is installed.

Now stick to these actions to show multiple view controls.

1. Log in as the host user, open the extensions page, and click the edit icon to edit your module
   
   

   

2. Your module already has a default definition that typically includes a view, edit and settings control.  The setup looks something like the picture below.  (Note: In editing this image I accidentally shortened the source paths.  The format should be DesktopModules/My Custom Module/View.ascx)
   
   

   

3. Click the “Add Definition” link next the “Select Definition” drop down.
   
   

   

4. On the new screen fill in the information to create the new definition and click “Create Definition”.  In this case I’m calling it “Definition 2″, but you’ll want to make your definition names descriptive, or whatever meets your naming convention needs.
   
   

   

5. Now you’ll have a fresh new module definition to fill out just like the default definition.
   
   

   

6. You can now add new module controls to the definition.  Click the “Add Module Control” link and fill out the form as a new View control by leaving the “Key” field blank.  Fill in the title field, select the source and leave the Type as “View”.
   
   

   

   
   
7. Update the definition and navigate to the web page in which you would like to incorporate the module. Incorporate the module towards the webpage. In the event you had already additional the module you’ll require to delete it and incorporate it once again or else DotNetNuke will not operate the code to add all of the see controls. Once you incorporate the module you ought to see each check out handle you produced a definition for look around the page as being a individual module occasion. In the event you do not, return and verify you accomplished the steps properly.
8. At this time whatever check out controls you really don't want to look on the web page, merely delete that instance from the module.
   

The Visual Studio Starter Kit enables you to create a compiled DotNetNuke module that can be much more compact, more quickly, and hide your supply code from prying eyes. The subsequent instructions can get you started and well in your approach to creating compiled DotNetNuke Modules.

1. Download the Starter Kit
2. Open Visual Studio  and create a new project (File -> New Project)
   
   

   

   From the dialogue follow these steps
   
   
   • Select Web from the Installed Templates. I use of VB.Net, but they are available in C# too.
   • Pick DotNetNuke Compile Module from your Project Type list.
   • Enter your Module Name
   • Enter the path for your DotNetNuke installation. Your project will be installed within the current set up within the DesktopModules folder and also the dll will likely be place in the bin folder.
   • Click OK
3. Visual Studio will load up the venture within the Solution Explorer and open the Documentation.html in the editor. You’re not however ready to set up the module so don’t keep to the DotNetNuke documentation but.
4. In the Solution Explorer right click on My Project and select Open.
   
   

   

5. Within the Application tab delete the entry in Root Namespace except if this is your only module, otherwise you will not be sharing code with other modules. I have a undertaking that spans numerous modules and i want them all inside the identical identify space. So, I delete the basis Namespace entry to ensure that I am able to put within the appropriate namespace from the code driving. (Edit regarding Root Namespace; in C# you do not need to clear the namespace, but in VB.Net you are doing).
   
   

   

6. Switch towards the Compile tab. Verify the Build output path and make sure its pointing towards the proper bin folder. Now simply click the Advance Compile Option on the button of the tab. Around the dialogue make certain the target framework is correct. You’ll see the environment on the base of the dialogue. At this point the dialogue will immediately near.
7. Repeat step 4 (open the project properties) then go to step 8
8. Switch to the References tab.  You should see a reference to DotNetNuke.Library version 0.0.0.0.  Remove it.
   
   

   

9. Nonetheless around the References tab, now click the Add button. Inside the Add Reference dialogue switch to the Browse tab and navigate for the DotNetNuke set up bin folder. Choose the DotNetNuke.dll, DotNetNuke.Web.dll, as well as the Telerik.Web.UI.dll. Should you do not hold the Telerik.Web.UI.dll then you definitely should not be making use of those controls and you also will not want the dll. Click Okay. These references are necessary to obtain access to the DotNetNuke methods and properties. In any other case you are code powering will be crammed with inexperienced and blue underlines, missing references, and, oh yeah, it won’t compile. Sort of defeats the aim, proper?
   
   

   

   
   
   Intellisense; this step is optional, but if you want Intellisense you’ll want to do this.  Switch to the Web tab. Under Servers select the “Use Local IIS Web server” option.  Change the Project URL to the full URL of your project (eg http://{domain}/DesktopModules/{project folder}).  Check “Override application root URL” and set it to the domain of your DotNetNuke install (eg http://{domain})
10. Save the Project Properties and close it.
11. Inside the Solution Explorer increase the Components folder and open up the ModuleNameController.vb (or .cs) file. Check the Namespace declaration and you’ll see that it states “YourCompany”. Change this to your customized namespace identifier and after that do the identical in each of the code powering documents. You will also need to change it inside the .ascx files because they’ll be reference the namespace inside the handle declaration at the best of the webpage.
12. At this point you can Build your project and you will see the new dll in your DotNetNuke install bin folder.
13. Now follow the instructions in the documentation.html to install the module in DotNetNuke.  Once the module is installed you don’t really need the documentation folder, or it’s files.  I usually delete it.
    
    

Obtaining up and operating with all the templates is really pretty straightforward, but you must stick to some really certain measures, not subsequent the measures tends to make it hard for anyone else in order to assist you as you can configure issues any number of ways that might cause difficulties.

Configuring your Development Atmosphere

This really is 1 from the most significant steps from the procedure, the templates are configured to operate in a site You'll find a couple of assets for placing up your environment. The crucial thing for your new release of the templates is you need to have DotNetNuke 7.3 operating at dnndev.me, unless of course needless to say you modify the templates your self, but that's outside of the scope of this weblog post.

Putting in the Templates

Installation in the templates is pretty simple, you'll find numerous techniques to complete this, select one in the a few choices beneath and carry out the actions outlined for the option you decide on. You simply have to do one of those choices, not all three.

1. Put in utilizing the Tools\Extensions and Updates menu in Visible Studio 2012
   
   • Mouse more than the Tool menu
   • Click on Extensions and Updates
   • Search for DotNetNuke
   • Select the Put in button to the DotNetNuke Project Templates option
2. Install manually by downloading the VSIX file from the online gallery
   
   • Pay a visit to the Visual Studio Gallery - DotNetNuke Project Templates page
   • Download the VSIX file via the Obtain website link.
   • Double click the downloaded file to install the templates.
3. Set up manually by downloading from Codeplex
   
   • Down load the VSIX file from Codeplex
   • Updated - Right Click the downloaded VSIX and choose Properties
   • Click the UNBLOCK button before proceeding
   • Double click the downloaded file to install the templates.

Making your Visual Studio Project

As soon as you have put in the templates, you can set up a project based on the templates. To do so you need to stick to the steps under

1. Set up Visual Studio 2012 (you need to have this done presently)
2. Install the undertaking templates as instructed above
3. Setup your DotNetNuke Advancement Environment as instructed over
4. Operate Visual Studio 2012 as an Administrator (correct click on the shortcut to do so)
5. File -> New Project
6. Choose possibly C# or VB.Net from your Languages segment of the new Project dialog
7. Pick the DotNetNuke Folder under your preferred language (C# or Visual Basic)
8. Choose possibly DotNetNuke C# Compiled Module, DotNetNuke VB.Net Compiled Module, DotNetNuke 7 C# DAL2 Compiled Module or DotNetNuke 7 VB.Net DAL2 Compiled Module for the project template.
9. For the new project creation screen using the following settings
   
   • Title: ModuleName (something distinctive here, instance MyModule)
   • Place: c:\websites\dnndev.me\desktopmodules\ (this assumes you set up your improvement surroundings as instructed in Step 3)
   • Solution: Create new solution (this option might not be exhibited, that's okay)
   • Create directory for solution : Unchecked (this may trigger route issues if checked, the templates presume the SLN is inside the same folder since the project file)
   • Add to source control: Unchecked (I typically get my undertaking operating before incorporating it to supply control)
10. Click Ok
11. In certain cases Visual Studio will change the DesktopModules folder in into a Digital Listing, this will cause problems with your DNNDEV.me environment, load IIS Supervisor (start>run>INETMGR) and take away the Virtual Directory if it appears as a single there.

Installing your Module in Improvement

Once you create your project in Visual Studio 2012 the module will exist within the c:\websites\dnndev.me\desktopmodules\MyModule folder, but it is not technically installed and registered with DotNetNuke. To complete that you need to execute the follow steps.

1. Develop your Project in DEBUG mode.
2. Modify to Release mode and build again.
3. Login to your improvement website within a browser, using a HOST/SuperUser account.
4. Navigate for the Host/Extensions web page
5. Pick the Install Extension Wizard option
6. Simply click Choose File
7. Browse to your c:\websites\dnndev.me\desktopmodules\MyModule\Install\ choose either the INSTALL or SOURCE package to upload.
8. Go through the measures for the installation wizard (if the module fails to install, attempt closing Visual Studio very first, then set up the module)
9. Location your module on a page (I usually produce a fresh webpage for each module in my development environment for tests reasons).

Setting up your Module in Production

To install your module in production you'll keep to the same actions as installing it inside your improvement environment, other than you will nearly Never utilize the Source package of the module in creation, it just is not essential.

What’s Subsequent?

So I lastly received the 7.0 (7.3) templates out the door, what is subsequent? Reworking the DNNTaskManager module which i created a module advancement tutorial for back in 2011. The program is to actually rewrite that module from the ground up utilizing DNN seven.0, in a few distinct iterations. 1) Utilizing the unique DAL design in DotNetNuke, 2) Using the new DAL2 template, 3) Utilizing ContentItems in DotNetNuke 7. Keep tuned to my weblogs to learn more as those tutorials are produced.

Certainly one of the commonest queries which i get by way of the community forums on this website, or via e-mail is "How does one get your websites to operate so fast". Although not excellent, my web sites normally operate somewhat more quickly than your typical DotNetNuke 7.3 websites. Formerly I have stored the exact particulars of my changes to myself, nevertheless, with a litle encouragement from the neighborhood I've chose to share the full context of the changes that i make into a default DotNetNuke set up to acquire better baseline performance, as well as added products that i do to aid when i actually want that "boost".

Overview

To begin with I want to begin out by declaring that a great deal in the details that's shown listed here could be located in previous website postings. Posts this sort of as DotNetNuke Host Options Explained, DotNetNuke Scheduler Explained, DotNetNuke Overall performance Options Defined, and straightforward DotNetNuke Performance Enhancements. Are good beginning factors for a few of the element driving my recommended adjustments.

The subsequent changes are merely the configurations that i have found for being the very best "baseline" configurations. Consideration is required in regards to the web site setup, update frequency, traffic, hosting environment and users to ensure that you have the correct set up for your particular atmosphere. I'll talk about the options section by segment, merely noting the modifications which can be created. Remember to reference the specific "Detail" doc for more information.

DISCLAIMER: Adhere to these suggestions as a manual only, I am not responsible for any results of employing these adjustments.

Host -> Host Options Changes
The first place I pay a visit to may be the Host Options page. There are a selection of key updates and adjustments required on this segment. Again, only changes are noted right here.

Appearance
In this segment I uncheck the "Show Copyright Credits" box

Advanced -> Authentication Settings
Within this segment I uncheck "Enabled" for almost any provider that will not be utilized in the portal, normally the LiveId and OpenId companies

Advanced -> Performance Settings
On this area I change the "Module Caching Method" to Memory. the "Performance Setting" to HeavyCaching. As well as the "Compression Setting" to GZip Compression.

Advanced -> Other Options
In this section I modify the "Scheduler Mode" to Timer. I enable the "Event Log Buffer" and i disable the "Auto-Sync File System" alternative

They are the commonest Host Options adjustments which i total. Based within the website I'll make a couple of other little edits.

Host -> Scheduler Changes
The largest alter that i make right here would be to modify the "SearchEngineScheduler" task to run normally as soon as every 12/24 several hours. This reduces a big load around the server.

Other Modifications
From a DotNetNuke configuration alter which is all that I modify. Overall these adjustments typically outcome in extremely noticable efficiency advancements, but often times it just isn't adequate to maintain the web sites operating as smooth as possible. So according to the specific situation I have numerous other things which i function with.

Normal Purging of Occasion Log
As a lot of people which have utilized DotNetNuke have identified the EventLog table could become a very troublesome hinderance within the performance facet of a web site. Enabling the Event Log Buffer helps reduce the consequences of the huge EventLog, nonetheless, the most effective policy is always to thoroughly clean the EventLog on a normal foundation.

I try this one of two methods. By myself sites I have an SSIS package deal inside of SQL Server that truncates the desk each 24 hrs. On customer web sites I make use of my Scheduled SQL Employment module to keep a seven working day rolling historical past of the EventLog information. The key here is the fact that we must keep the occasion log tiny.

Skin Choice and Menu Provider
The next item of thought is actually a multi-part thought. I target on finding CSS primarily based pores and skin layouts that use 3rd party menu parts this sort of as Telerik and Css NavMenu. With a straightforward pores and skin modify to sites I've seen webpage load occasions which have decreased by more than 50%.

Discovering an excellent designer that creates well laid-out skins with 3rd get together menu suppliers is a crucial overall performance enhancement, a minimum of in the page. I've NOT benchmarked these numbers although because DNN 4.six.2, so the core menu company might have much better performance.

Compression/Caching Modules
Like a last stage, if I actually need to get the most performance out of a website I will often lean towards Snapsis PageBlaster as being a good alternative. I at present use PageBlaster on this website only and also have had really excellent luck with it, though when configuring the module you have to be cautious to test all functionality very first. This was another change that after applied I seen really noticeable efficiency advancements.

With all the introduction of the DDRMenu to DotNetNuke, we've experienced much more manage above what is rendered from the menu. This has authorized for a a lot more semantic menu and custom made styling for easy menus to mega menus. There are numerous methods to create the template that the DDR makes use of but we'll be using the token primarily based templating because it is quite easy.

Menu Template (Bootstrap Nav)

I copied the easy folder from your Gravity pores and skin that will come with DNN 7, which incorporates a manifest file “menudef.xml” and the “SimpleToken.txt” file. I updated the SimpleToken.txt file as follows:
Notice: this isn’t a tutorial on DDRMenu, just how to apply Bootstrap.

<ul class="nav nav-pills">
    [*>NODE]
    </ul>
    [>NODE]
        <li class="[?NODE]dropdown [/?][?SELECTED]active[/?]">
        [?ENABLED]
            <a href="[=URL]">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [?ELSE]
            <a href="#">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [/?]
        [?NODE]
            <ul class="dropdown-menu">
            [*>NODE]
            </ul>
        [/?]
        </li>
    [/>]

1. Add the classes nav and nav-pills to the outer ul. Individually, I favor the simplicity in the Simple tablets nav that bootstrap gives. This appears to be the easiest to override with my own custom design and style as I have a tendency to use more flat UI’s in my style.
2. Include the category “dropdown” for the list merchandise if it's youngsters using the [?NODE] examination.
3. Add the category “active” for the listing product whether it is selected utilizing the [?SELECTED] examination.
4. Add a caret to the merchandise if it's a baby item.

Up coming, we are able to include the HTML and pores and skin object within the pores and skin as follows:

Logo and Menu pores and skin objects (Bootstrap Navbar)

<div class="navbar">
        <div class="navbar-inner">
            <span class="brand">
                <dnn:LOGO runat="server" id="dnnLOGO" />
            </span><!--/Logo-->
            <dnn:MENU MenuStyle="Simple" runat="server"></dnn:MENU>
        </div><!-- END navbar-inner -->
    </div><!-- END navbar -->

1. add link with class “btn” and btn-navbar”. Also, requires markup for collapse. You are able to use either JavaScript or information attributes.
2. Wrap dnn:MENU pores and skin item using a div using the adhering to class
   “nav-collapse” and “collapse” - this permits the menu to break down at smaller display screen sizes
   “pull-right” to drift the menu to the correct side, if you so desire.

Note: making use of this process will disable a menu merchandise which has children. In order that this is a click to open up motion. This can be to make things function much better for contact units.

The Simple Way to Install DotNetNuke

DotNetNuke is a Web-content management platform for those who use the Microsoft ASP.NET framework. Based on your company needs, whatever version of DNN you choose, it will be a significant cost saving venture over other options. Installing DotNetNuke is not a task well-suited for beginners to this sort of website framework. If you are familiar with websites, databases, and ASP.NET, you can use these instructions to learn how to install DotNetNuke.

Check the DotNetNuke installation requirements before getting started. To install DotNetNuke, you need a database with either Microsoft SQL Server 2005/2008 or SQL Express. If you have an older version of DotNetNuke 5.2 or earlier, you can use SQL Server 2000. You should also have a Microsoft IIS (Internet Information Services) with version 5 or higher, and the Microsoft .NET 3.5 SP1 framework. This service pack is available through the Windows Update feature.

Download the latest version of DotNetNuke to your computer, and unzip the file.

Use the FTP software of your choice to connect to your website, and upload the installation files into the directory of your choice. If necessary, create the directory where you want to install DotNetNuke on your server.

Select the folder where DotNetNuke is located. Click "Properties," choose the "Security" tab, and add the necessary user permissions. Use either the local ASP.NET service (for Windows 2000 and XP) or the local Network Service account (for Windows 2003, Vista, 2008, or 7). You should have permission to modify the folder.

• Open the IIS server console. Go to "Start" > "Run" > INETMGR. Click on the "websites" node, and select the "Default website" node.
• Right click on the DotNetNuke folder. Click "Convert to Application." If this option is not available, select "Properties" and add the application.

Install DotNetNuke with SQL Express.

• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. The database information should already be configured, and you should not need to change it.
• Look for the default login information for the "host" and "admin" users, which is shown when installation is complete.
• Log in immediately, and change the passwords to protect against hacking.

Install DotNetNuke with SQL Server 2005/2008 for your database server.

• Open SQL Management Studio, and connect to your database server.
• Walk through the installation wizard as presented on the screen.
• Create a new database by expanding the server node, then the databases node, and filling in necessary values for all the database properties.
• Set up the SQL user and security account, and choose the appropriate integrated-security or user-security setting under the "server/security" node.
• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. Choose SQL 2000/2005/2008, and follow the security steps according to the option chosen in the previous steps. Test the database connection.
• Finish the installation wizard, and look for the default login information for the "host" and "admin" users.
• Log in, and immediately change the passwords for those accounts to protect against a hack.

Best and Cheap DotNetNuke Hosting Provider

Are you looking for best and cheap DotNetNuke Hosting Provider? ASPHostPortal is the answer. ASPHostPortal.com is a windows-based hosting service provider. ASPHostPortal.com offers the most reliable and stable DotNetNuke 7.3 web hosting infrastructure on the net with great features, fast and secure servers. Our hosting can be done via USA, Amsterdams or Singapore based server. Depending on your requirements, we can scale so we can deliver the right service for the right price. All of our windows hosting plan supports DotNetNuke 7.3 and you can install DotNetNuke 7.3 with just one click.

Cart Viper is The Best DotNetNuke eCommerce Solution

If you read this article, of course you interest with ecommerce. In this article, we will tell you that you now you will develop your online store easily with DotNetNuke platform. If you are already using DotNetNuke then you will know what a great platform it is to build rich and engaging websites but what if you could use the same platform to run an online DNN shop?

Why you should using Cart Viper?

Cart Viper is an ecommerce solution built for DNN providing a PCI compliant online store for your business. You will start to sell online today using the simple to use ecommerce store easily. From now you will sell anything; physical products, digital downloads and events. Using Cart Viper you can create a fully functioning online shop within 30 minutes.

Is Cart Viper The Best DotNetNuke Store?

The answer absolutely is YES. In their official website, they said that, “Since starting Cart Viper we've added hundreds of new features and improvements all with the aim of making the best dotnetnuke store available on the market. A great product is no good without great support so we are dedicated to providing help and support so that you can get the best out of our product. Take a look at the feedback we have received from our satisfied customers.”

Features of Cart Viper

There are some features of Cart Viper:

• Categories and Sub-Categories – You can create and manage an unlimited number of product categories. In here you also can find SEO optimized product categories page - define the category URL, META description and title tags.

• Products – You can create an unlimited number of products. Automatic re-sizing of product images (small, medium, large) based on your predefined image size.
• Product Variants - Choose the variant option display e.g. dropdown list, checkbox, radio button, textbox, multi-line textbox or image uploader. Track stock quantities for each product variant, so you know exactly how many of each product variation you have in stock.
• Catalog Localization - Ability to enter categories and products in multiple languages. Categories and products will fully localize to the current language that is being viewed by the user.
• Product Offers - Create and manage product offers. Define start, end date and offer price. Offer is applied and removed from a product without any user interaction.
• Coupons - Define rules for each coupon. e.g. minimum subtotal, can be used multiple times, start date, end date, customer email address, etc. Offer a monetary or percentage discount.
• Promotions - Create store wide promotions, so every product has a specific discount during the given period. Create category wide promotions, so every product in the category has the specific discount during the given period.
• Product Discount Bundles - Create product discount bundles where a user receives a discount if they purchase 2 or more items at the same time. Promote up-selling and maximise each sale via product discount bundles.
• User Specific Pricing - Define a product price for a specific user of your DNN site. Define a product price for a specific role of your DNN site. When browsing the store the individual user price is displayed to that user.
• Digital Downloads - Define which products have a digital download. Digital downloads now support PDFs as a valid file type. Allow admin to define how long / how many times a user can download a digital download after they have purchased it.
• Product Comparison - Allow users to select up to 4 products then compare them side by side! Store admin defines the product details they can compare e.g. weight, size, model number etc. Allow the user to quickly and easily see the advantage of 1 product over another.
• Wishlists - Wish list automatically updated if admin deletes / edit a product in a user’s wish list. Anonymous users can create wish lists, and then they will automatically be transferred into their user account if they then sign in to your store. Customers can make their wish list public and send friends a link to view the wish list.
• Product Visualizer - Allow a user to see a mockup of what their product will look like once they have made their specific choices. e.g. select text or upload an image.
• Product Reviews & Ratings - Enable / disable product reviews. Product average rating calculated from customer reviews. Product reviews approved by admin before appearing on site.
• Shipping - Enable / disable shipping to be calculated on an order. Support an unlimited number of shipping providers so customer can select when they checkout e.g. FedEx, UPS, default, etc
• Tax & VAT - Based on stores location and the users billing address Cart Viper automatically works out if you need to charge VAT or tax. Define VAT rates for: Zero rated product,Reduced rate products & Standard rate products. Assign each product to a VAT rate.
• Payment Methods - Let customer pick between online or offline payment methods at the point of checkout. Real time credit card payments (Mastercard, VISA, Solo, Switch, Amex and Discover). Accept offline payment methods (cash on delivery, cheque, purchase orders, etc) with or without Real time payment method as well.
• Payment Gateways - Optional ability to apply a percentage or fixed amount surcharge to an order placed with Paypal Standard. Recurring billing support when using Authorize.net payment gateway, manage subscriptions directly from Cart Viper, recieve notifications when card declined.
• Cart & Checkout - Advanced jQuery add / edit / delete items shopping cart functions. Separate mini-cart control that can be added to any content pane. User friendly wizard style checkout screen.
• Store Administration - Quick Install for Creating a New Store. Simple intuitive administration UI. Optionally assign DotNetNuke roles to admin tasks as product management, order management etc. Product moderator feature - create a new setting that allows the a DNN role to be entered users with this role can add products however they need to be moderated before appearing in the store front.
• Catalog Workflow and Version History - Define if that all changes to the store catalog requires moderation. Ability to accept / decline changes, with email notifications.
• QuickBooks Integration - Automatically transfer orders from Cart Viper into QuickBooks.
• Order PDF - Store admin or customer can download a PDF receipt of any order that has been placed. Admin can define an image along with header and footer text to brand the PDF as per your needs.
• Sales Reporting - Cart Viper automatically calculates your sales data for the current day and at a glance allows you to see how that compares to yesterday and the average of the last 30 days. View sales data by product or category for specific date you enter. Export sales data to .XLS format.
• My Account Module - Separate my account module included. Edit their account profile settings - billing / shipping address etc. Users can view / search through their order history.
• Product News Letter - Separate product newsletter module, allow users to sign up to your store product newsletter. Product newsletter automatically sent with no human interaction.
• Product Widget Module - Separate product widget module that can be used to display products anywhere on your DNN portal. Select products to display in product widget module by: random, top sellers, by category, individual selection, products currently on special offer and newly added.
• RSS 2.0 Feeds - Optionally expose RSS 2.0 feeds based on the product data in your store. 3 different RSS 2.0 feeds: top selling products, newly added products and featured products.
• HTML Email Templates - All emails that the store sends are HTML based so you can customize then to suit your needs. Fully HTML enabled so you can brand the emails as per your needs using CSS and images.
• Define the Store Currency - The following currencies are supported by Cart Viper: United States Dollar (USD) , Great British Pound (GBP), Euro (EUR), Australian dollars (AUD), Canadian dollars (CAD), Mexican peso (MXN) Swiss francs (CHF), Singapore dollar (SGD), Thailand Baht (THB), New Zealand Dollar (NZD), Phillipine Peso (PHP), Czech Koruna (CZK) and Mexican Peso (MXN).
• Donations - Optionally allow customers to place donations. Define predetermined amounts with the customer able to select or enter their own donation amount. Allow the customer to enter a name associated with the donation.
• Multi-language Support - They currently have the resource files translated into English, French, German, Spanish and Dutch. However Cart Viper can be translated into any language you require!
• Multiple Portals Supported - Cart Viper can be installed on multiple parent and child portals. Each portal would need to have its own license.
• Advanced Templating - Razor Template Support. Responsive store template, create a great store experience for desktop, tablet and mobile users. Data and presentation kept separate allowing you to create your own templates without any programming knowledge.
• Google Analytic eCommerce & Event Tracking - Full eCommerce & event tracking support integration into Google analytics. Track 25 different events inside your store. Provides detailed statistical analysis how customers are users your store. Quickly and easily find customer trend and shopping habits!
• DotNetNuke Versions Supported - Cart Viper requires version 5.x, 6.x, or 7.x of DotNetNuke. Works in both Full Trust and Medium Trust environments.

Best and Cheap DotNetNuke Hosting for Your DotNetNuke Site

ASPHostPortal.com is the best and cheap windows-based hosting service provider. ASPHostPortal.com offers the most reliable and stable DotNetNuke 7.3 web hosting infrastructure on the net with great features, fast and secure servers. Our hosting can be done via USA, Amsterdams or Singapore based server. Depending your requirements, we can scale so we can deliver the right service for the right price. All of ourwindows hosting plan supports DotNetNuke 7.3 and you can install DotNetNuke 7.3 with just one click.

DotNetNuke is an open source CMS based on Microsoft .Net technology. DotNetNuke can be easily installed and hosted. In general, DotNetNuke framework allows individuals to do whatever they wish with the application framework both commercially and non-commercially, with the simple requirement of giving credit back to the DotNetNuke project community. In this article, I will tell you how to automate the packaging of your DNN Module.

DotNetNuke is a program that runs on Microsoft ASP.NET. It is also a framework, meaning, it is a program that is designed to be extended. One of the ways you extend the framework is to create modules. These modules are installed inside a DotNetNuke installation and when they run in that DotNetNuke installation they extend the framework to create a DotNetNuke website also called a portal.

Here are the steps for automate the packaging of your DNN Module:

• Delete all source code and start over from scratch with my templates installed. If you really don’t want to go through step #1, you can skip it, but you must then go on to Step 2 below

• 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

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.

What is DotNetNuke?

DotNetNuke Platform, formerly called DotNetNuke, is a free, open source website builder and content management system based on the .NET framework. It is a tool designed to be used from a web browser that can create any type of website, from small business sites to online communities and intranets. In this article we will tell you about how to integrate DotNetNuke with SharePoint.

Integrate DotNetNuke with SharePoint

1. Good knowledge of SharePoint and DotNetNuke - This particular approach helps in easy as well as seamless integration of both the document management system and the software making it easy for content monitoring along with modification. It is important to have good knowledge of the software as well as the application before taking up integration.
2. Always integrate with SharePoint 2007 and 2010 – This particular objective helps you enjoy the best benefits of both the DotNetNuke along with the document management system. After all, it helps publishing fresh contents extracting it straight from the SharePoint Document library. The published documents are carefully protected by the role based security network of DNN. 
3. Always publish documents that are approved for display – Undertaking this particular approach always helps you to avoid any sort of interference with the team. This helps you ensure the use of a streamlined alongside a collaborative procedure that helps in effective management of the document. Additionally, it also allows you to share the best documents that are carefully edited and ready for use. 
4. Ensure consistent permission throughout the work – This particular objective if maintained right helps preventing any sort of unauthorized access thereby, ensuring a secure digital asset management. Additionally, it also helps preventing the redistribution of assets that are digital. 
5. Make use of views and not folders – This helps you ensure having unlimited flexibility along with extreme level of granularity. It is also important for you to be able to combine the properties easily and this particular approach helps in successful combination. The biggest advantage rests with the fact that it helps reducing overall risk alongside human error. 
6. Synchronize the deletes – Taking up this particular approaching during the process of integration also helps avoiding the errors of “file not found” during the successful execution of removal of files. This particular approach of cleaning also ensures reduction of unimportant database clogging, duplication, overall risk, and human errors. 
7. Enabling of error notification is must – This specific task helps in automatic synchronization eliminating the need of active viewing or monitoring of the document in concern. This result in a smooth process that helps you to lessen the effort along with the time required for content monitoring. 
8. Avoid the firewall – Always make sure that the SharePoint server can enjoy an easy access to the DotNetNuke server. This helps in smoother as well as better content management without any modification of security policies. 
9. Allow filtering of documents to be transferred – This particular approach helps the users to filter the documents easily through the integrated SharePoint filtering views. This helps the users to make use of the Create View UI and need not rely upon two different sets of filters.

Is DotNetNuke The Best Application for Developers, End Users and Organization?

Based on the.NET framework by Microsoft, DotNetNuke is a content managing system for websites. One of its advantages is the fact that the framework's Community Edition is open-sourced and has an MIT free software license, allowing free download, usage, modification, and extension. This, combined with the modular structure of the framework, has allowed various third-party developers to write and publish additional modules and upgrades to the basic package. Professional and Enterprise editions of DotNetNuke are paid for, but offer better tech support and certain features critical for business-level web-site management. However, the Community edition also receives a lot unofficial tech support from the extensive user and modder community.

DotNetNuke for Developers

DotNetNuke is a brilliant combination of Content management System (CMS) and Web application development framework. This adaptable architecture allows developers to effortlessly add functionality or make changes in the look of the website through addition of DotNetNuke applications. There are lots of websites where you can find free applications, you can use or customize these applications according to your need. That is reason DotNetNuke has become the first choice of developers.

DotNetNuke for End Users

DotNetNuke is very good tool for end users as they can within minutes post contents on the websites.This powerful and simple tool allows end users to modify the content without support from IT personnel.

Systems administrators find the granular security model very useful as they can define accessing rights for the end users. Both end users and administrators find it extremely helpful as the end users enjoys the freedom to post and modify content as per their wish and system administrators need not to be bothered about the rest of the website being modified as they have defined the extent of access.

We are in an era where internet is considered to be the principal source to find out reliable information. It gives you a platform to reach out to people and to know about their views also.People can write their views and it gets online for others to read.A positive article will absolutely add feather in your cap but a wrong or misleading one can spoil image of the company. Content Approval Workflow feature is the perfect solution for it and it takes web content controls one step ahead. In this your website is configured with custom approval workflows so whatever changes is made to the website, needs to be approved by authored person before it gets online. This helps you to monitor the quality and content of the article. This path breaking Content Approval Workflow feature is available in DotNetNuke Enterprise and Professional Editions.

DotNetNuke for Organization

Organization needs to make changes to websites on a regular basic. The flexible and reliable Content management platform of DotNetNuke allows organization to swiftly execute wining web strategies.Using DotNetNuke application you can easily control and change the look of the website.

The DotNetNuke Enterprise and Professional edition are reasonably priced and have very good technical support. Their free edition is known as Community Edition which you can download from internet and use it.