DotNetNuke Hosting with

BLOG about DotNetNuke CMS, latest technology and Special DotNetNuke Hosting Package with

DotNetNuke - :: Tips To Make DotNetNuke Sites Run So Fast

clock April 28, 2016 20:08 by author Armend


First of all I want to start out by saying that a lot of the information that is displayed here can be found in previous blog postings.  Posts such as DotNetNuke Host Settings Explained, DotNetNuke Scheduler Explained, DotNetNuke Performance Settings Explained, and Simple DotNetNuke Performance Enhancements.  Are good starting points for some of the detail behind my recommended changes.


The following changes are simply the configurations that I have found to be the best "baseline" configurations.  Consideration is needed in regards to the site setup, update frequency, traffic, hosting environment and users to ensure that you have the proper setup for your specific environment.  I will discuss the settings section by section, simply noting the changes that are made.  Please reference the specific "Detail" document for more information.

DISCLAIMER: Follow these recommendations as a guide only, I am not responsible for any effects of implementing these changes.

Host -> Host Settings Changes

The first place I visit is the Host Settings page.  There are a number of key updates and changes needed in this section.  Again, only changes are noted here.


In this section I unchecked the "Show Copyright Credits" box

Advanced -> Authentication Settings

In this section I unchecked "Enabled" for any provider that will not be used in the portal, typically the LiveId and OpenId providers

Advanced -> Performance Settings

In this section I change the "Module Caching Method" to Memory.  the "Performance Setting" to HeavyCaching.  And the "Compression Setting" to GZip Compression.

Advanced -> Other Settings

In this section I change the "Scheduler Mode" to Timer.  I enable the "Event Log Buffer" and I disable the "Auto-Sync File System" option
These are the most common Host Settings changes that I complete.  Depending on the site I'll make a few other small edits.

Host -> Scheduler Changes

The biggest change that I make here is to change the "SearchEngineScheduler" task to run typically once every 12/24 hours.  This reduces a big load on the server.

Other Changes

From a DotNetNuke configuration change that is all that I modify.  Overall those changes typically result in very noticeableperformance improvements, but many times it just isn't enough to keep the sites running as smooth as possible.  So depending on the situation I have a number of other items that I work with.

Regular Purging of Event Log

As most people that have used DotNetNuke have discovered the EventLog table can become a very troublesome hindrance on the performance side of a site.  Enabling the Event Log Buffer helps reduce the effects of a large EventLog, however, the best policy is to clean the EventLog on a regular basis.
I do this one of two ways.  On my own sites I have an SSIS package within SQL Server that truncates the table every 24 hours.  On client sites I utilize my Scheduled SQL Jobs module to keep a 7 day rolling history of the EventLog data.  The key here is that we MUST keep the event log small.

Skin Selection and Menu Provider

The next item of consideration is a multi-part consideration.  I focus on finding CSS based skin layouts that utilize third party menu components such as Telerik and Css NavMenu.  With a simple skin change to sites I have noticed page load times that have reduced by over 50%.
Finding a good designer that creates well laid-out skins with third party menu providers has been a key performance enhancement, at least in the page.  I have NOT benchmarked these numbers though since DNN 4.6.2, so the core menu provider might have better performance.

Compression/Caching Modules

As a last step, if I really need to get the most performance out of a site I will tend to lean towards Snapsis PageBlaster as a good option.  I currently use PageBlaster on this site only and have had very good luck with it, although when configuring the module you must be careful to test all functionality first.  This was another change that once implemented I noticed very visible performance improvements.


There you have it, that is my secret trick to improving DotNetNuke site performance!  Many people charge a lot of money to make these simple performance tweaks and I just laid them all out on the table for you free of charge.

DotNetNuke Hosting - :: GetTab Method without DNN Context

clock April 27, 2016 00:54 by author Dan

As you know, the simple method GetTab(int tabid) was obsolete and has been replaced by GetTab(ByVal TabId As Integer, ByVal PortalId As Integer, ByVal ignoreCache As Boolean). If you want to call the new method, we have to pass the additional parameter “PortalId”.

In common,  the object PortalSettings can be easy to get with DNN context, such as special dnn module & page; however, it may be inaccessible in some sceneries, such as separate aspx page or handler. Then is there any way to get the correct tab info with this new method? Now there is a simple trick to do it with passing into Null.NullInteger as the parameter PortalId. So the coding looks like that:

var tabController = new TabController();
var blogPage = tabController.GetTab(tabID, Null.NullInteger, false);

Deeping into the source code, you will find out that it always tries to get the correct PortalId for this tab/page object:

//if we do not know the PortalId then try to find it in the Portals Dictionary using the TabId
portalId = GetPortalId(tabId, portalId);

//if we have the PortalId then try to get the TabInfo object
tab = GetTabsByPortal(portalId).WithTabId(tabId) ??
        GetTabsByPortal(GetPortalId(tabId, Null.NullInteger)).WithTabId(tabId);

Hope this trick & tip helps if someone has the same issue.

Best DotNetNuke Hosting Recommendation provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice. Announces ASP.NET Core 1.0 Hosting Solution

clock April 26, 2016 23:34 by author Dan is a well-known Windows hosting company and even one of the most famous, though it is one of the oldest Windows hosting companies. Our packages have gone through major changes recently, and all of them goes for the goodness of every customers. Today, we launch ASP.NET Core 1.0 hosting with interested hosting packages.

3 months ago, the ASP.NET team announced during the weekly ASP.NET Community Standup was decided to rename ASP.NET 5 to ASP.NET Core 1.0. The whole “ASP.NET 5 MVC 6 Web API 2 sub-component version scheme was confusing. They’ve been working towards “One ASP.NET” now for years and they’re there. ASP.NET Core is versioned as 1.0 as it’s a near complete rewrite of ASP.NET with many new features and capabilities. It’s clearly a different product than ASP.NET 4.6.

.NET Core is a modular, streamlined subset of the .NET Framework and CLR. It is fully open-source and provides a common set of libraries that can be targeted across numerous platforms. Its factored approach allows applications to take dependencies only on those portions of the CoreFX that they use, and the smaller runtime is ideal for deployment to both small devices (though it doesn’t yet support some) as well as cloud-optimized environments that need to be able to run many small applications side-by-side. Support for targeting .NET Core is built into the ASP.NET 5 project templates that ship with Visual Studio 2015. offers ASP.NET Core 1.0 Hosting with an interested hosting plan. We support this new technology with affordable price, a lot of ASP.NET features, 99.99% uptime guarantee, 24/7 support, and 30 days money back guarantee. We strive to make sure that all customers have the finest web-hosting experience as possible. To learn more about our ASP.NET Core 1.0 Hosting, please visit

About is The Best, Cheap and Recommended ASP.NET & Linux Hosting. has ability to support the latest Microsoft, ASP.NET, and Linux technology, such as: such as: WebMatrix, Web Deploy, Visual Studio, Latest ASP.NET Version, Latest ASP.NET MVC Version, Silverlight and Visual Studio Light Switch, Latest MySql version, Latest PHPMyAdmin, Support PHP, etc. Their service includes shared hosting, reseller hosting, and Sharepoint hosting, with speciality in ASP.NET, SQL Server, and Linux solutions. Protection, trustworthiness, and performance are at the core of hosting operations to make certain every website and software hosted is so secured and performs at the best possible level.

DotNetNuke - :: How to Activate Google Analytics on Your DNN Site

clock April 19, 2016 00:07 by author Armend

How to Activate Google Analytics on Your DNN Site

You can't go wrong using Google Analytics (GA) to track the performance of your site. It has awesome reporting capabilities and you can't beat the price; it's free! And out-of-the-box DNN is fully integrated with Google Analytics. Just follow these instructions and you'll be running Google Analytics in a matter of minutes.

To Activate Google Analytics on your Site

  • Get your Google Analytics Account Number : Your first step is register you complimentary Google Analytics account. These is no charge for this GA account, and it takes just a couple of minutes to get your account number. Visit to activate your Google Analtics account; and click the Access Google Analytics button and follow the on-screen instructions. When you have your GA account number you are ready to go to Step 2 below.
  • 2 Install your Tracking Code : Google Analytics tracks your site activity through the use of a javascript snippet that contains your GA account number (also known as your tracking ID). This javascript tracking code must appear in the <head> section of every page you want to have tracked.

Good news—DNN automates this for you. All you have to do is add your GA account number to a field on your site and DNN takes care of the rest. Here's what you do:

  • Login to your DNN site using an Administrator account.
  • Go to the Admin | Google Analytics page. You will see a field where you enter your GA account number:
  • Paste your GA account number into this field and click Update.

That's it! Google Analytics will now start tracking your site.

Verify your Setup

It can take up to 24 hours for data to appear in your Google Analytics account after you've installed your tracking code. But in the meantime, you should take a minute to confirm that your tracking is setup correctly. You can confirm your tracking using any of the following options:

  • View Page Source Code : Take a quick look at the source of a page on your site to make sure your Google Analytics javascript is there. As long as you see javascript code similar to the following (with your own tracking ID value) of course, your setup is correct:

  • Check your Google Analytics Dashboard : Login to your Google Analytics account (  and click the Admin link. You should see a status of 'Waiting for Data.' This indicates that your code is correctly installed, but no data has been collected yet. If you return in roughly 24 hours you should see this status change to 'Tracking Installed' and you are good t


DotNetNuke - :: 12 Tips to Make SEO Easier in DNN

clock April 14, 2016 19:20 by author Armend

12 Tips to Make SEO Easier in DNN

Search Engine Optimization (SEO) is a cross-functional discipline and to achieve findable websites, a variety of tactics must be employed. When building DotNetNuke (DNN) websites, optimizing your websites for findability can be exceptionally challenging. Rich, contextual content is the root of findability, but due to the nature of a content management system (CMS), content can have many disparate sources and control of your content can be unwieldy. In this article, I’ll list 12 tactics to make maintaining the fundamentals of findability in DNN easier.


1. Start Using Semantic Markup in the Skin

Semantic markup is crucial to providing context to your content. As modules are added to the page to create the content of your site, additional markup is often a necessary evil in providing the features native to DotNetNuke. By using semantically correct markup in your skin, you’re boiling the cream to the top. Here are a couple of ideas to give you a taste of how to accomplish this on your sites:

  • Wrap the logo token with a H1 tag. The logo token will automatically generate an alt tag for the image set as your site’s logo. By wrapping the logo in a tag your sites’ title will have the highest priority on all pages. Depending on how far you want to take it, CSS text/image replacement may even be better.
  • Wrap footer links in tags. Copyright, privacy statements, terms, and other global links should be considered a paragraph of links, make the markup reflect this.

2. Avoid the Managed Content Trap

DotNetNuke is a content management system, but this doesn’t mean everything has to be managed content. Evaluate your content like it is a garden – consider which content needs to be replanted frequently (managed content) and  which content is like a shrub or tree (not tended to frequently, visible throughout your site).  Plant the shrubs in your skin and if they need to be changed make a change to the skin. By planting content in your skin files, the content will be less obstructed by markup and maintain the original design.

3. Put Database-Driven Content to Work

The content in DotNetNuke is stored in your database – use this feature to dynamically inject content onto your pages. There are a number of dynamic content elements you can utilize to introduce content to your pages without using modules. Timo Breumelhof offers a very good list of DNN Attributes in that can easily be included in your skin files.

4. Evaluate Navigation Providers

image demonstrating the title tag added to navigation items in DNN NavPay attention to the features of the navigation provider you’re using. Many of the providers available have hidden gems that provide more content to the navigation than simply the page titles. Our friend and core navigation provider, DNN Nav provides an attribute in which you can specify a tooltip for each menu. The tooltip will be automatically generated from the page name, page title, or page description.

5. Make Content Editing “Dummy Proof”

If you open your content management responsibilities to multiple users with a range of skills, you may come back to your site’s content to find it is riddled with missing alt and title tags and inline styles have been used to make headings instead of proper headings tags. This can do a number on the design of your site as well as the findability of your content. Be prescriptive about how you allows editors to manage their content and make the content editing tools “dummy proof.” Previously, I have blogged about customizing the rich text editors in DotNetNuke (Telerik editor and FCK editor). By customizing your rich text editor, you can shepherd your content editors toward semantic content.

6. Extend DNN to Make your Site Smarter

There are numerous modules in the DNN ecosystem that aid in improving the fundamentals of SEO. I could dedicate a separate blog to this topic alone, but the key consideration is to consider looking for modules to aid in keeping your content findable and search engine optimized. Let’s take one module specifically and dream a little together. iFinity Inline Link Master allows you do the equivalent of find and replace throughout your content. Wouldn’t it be great if you helped content editors by automatically creating external and internal links based on common words or phrases? You could even add in the rich attributes that many content editors neglect.

7. Consider File System Naming

For the next two topics you have to buy into the following theories – 1) content is more than just text and 2) file system paths add context to images and documents on your site. Are you still with me? Great. As you start to build out the organization of your file system, considering the naming of your directories and files plays a role in the findability of your content. More and more search findability is more than just text. Making sure the files on your site are findable and relevant to search terms can only help improve the overall findability of your sites.

8. Customize your Child Portals’ Directory

If your installation utilizes the multi-portal features of DotNetNuke, think twice as you create new portals. There is an often overlooked feature DNN offers allowing you to create a custom portal directory.

9. Make your URLs Friendlier

DNN has been making a slow journey toward a friendlier URLs. If you’re interested (and you should be) in moving faster toward full control over your URLs there are a number of extensions that will give you a long list of features make your URLs even friendlier
Let Search Engines Know
The first few tips were mainly focused on making your content semantic and meaningful to search engines. Once you have you have rich, semantically-correct content on your site you’ll want to reiterate to the search engines what you want them to find. Whether or not they’ll pay attention to you is beside the point. DotNetNuke offers a variety of features to guide search engines through your content.

10. Submit a XML Sitemap

Each DNN site automatically generates a XML sitemap (sitemap.aspx) Page Priority Starting in DNN 5.01, individual pages can have a specific priority assigned in the XML sitemap. Starting in version 5.01, DNN allows you to explicitly assigning page priority to your pages to instruct search engine bots on the hierarchy of your sites’ pages. Additionally, it is important to submit your XML sitemap to search engines.

11. Plug in a Third Party Sitemap Provider

In DotNetNuke 5.3, things got even better when DNN make the search engine sitemap a provider allowing modules to plug into the sitemap and allowing module developers to create custom search engine sitemaps to expand on the core’s functionality.

12. DNN Takes Care of Meta Content

The last consideration is not so much a task, but a reminder to take care of your page meta content. DotNetNuke does a lot of the work for you in generating Demonstrate the source of meta content in DNN. It is arguable as to whether this content is relevant or considered in search engine rankings, but it can’t hurt to provide more context for your site.


In conclusion, each of these tips could be a case study on their own and I’ve just hit the tip of the iceberg. If there was a concise way to summarize this article, it would be - search engine optimization can’t be an afterthought. If you consider your content from design to implementation to ongoing maintenance the only “optimization” will be in honing your message, not redoing your site.


We’re a company that works differently to most. Value is what we output and help our customers achieve, not how much money we put in the bank. It’s not because we are altruistic. It’s based on an even simpler principle. "Do good things, and good things will come to you".

Success for us is something that is continually experienced, not something that is reached. For us it is all about the experience – more than the journey. Life is a continual experience. We see the Internet as being an incredible amplifier to the experience of life for all of us. It can help humanity come together to explode in knowledge exploration and discussion. It is continual enlightenment of new ideas, experiences, and passions

Author Link

 photo ahp banner aspnet-01_zps87l92lcl.png

Corporate Address (Location)

170 W 56th Street, Suite 121
New York, NY 10019
United States

Tag cloud

Sign in