So I currently own a Hosting company that provides Windows ASP.Net and DotNetNuke hosting. DotNetNuke has been around for a while now and I see a increase in use and need for DNN providers.

I am trying to get more research on the needs for DotNetNuke. Does anyone have any comments, suggestions or insite on DNN Hosting etc.

For those that don't know what DotNetNuke is here is a short article I wrote to explain at a high level what DOtNetNuke provides.

Benefits Of Using DotNetNuke Websites

Internet has been one of the biggest phenomenons to hit the world in the last century. And in recent years, this phenomenon has constantly evolved to give the users better feasibility and a one stop solution for all their needs. In fact, web 2.0 has almost entirely changed the way we live our daily lives. Another recent development in the field of internet which is slowly gaining ground is that of DotNetNuke framework.

For the uninitiated, DotNetNuke framework is a content management solution meant for open source portals and managing your intranet needs. In short, it is a perfect solution for the needs of a small business who want to keep their investments to the bare minimum while increasing their productivity at the same time.

There are many benefits of using DotNetNuke websites. DotNetNuke websites have a whole lot of features which provides ease of use and flexibility to manage your day to day business needs. The benefits of using DotNetNuke websites are as follows:

 Ease of administration- With DotNetNuke, managing the website is a cinch. You do not need any technical expertise to load content on your site. All you need is basic computer skill and of course the content you want to load.

 Easy Interface- Another benefit of using DotNetNuke websites is their easy to understand interface. The framework is built in such a way that the user can handle and update each and every aspect of his/her project.

 Fantastic Tools- DotNetNuke comes with a set of fantastic tools which lets you control each and every aspect of your website. The tools help you deal with security issues, site membership issues and many such tasks that otherwise take up a lot of effort and time.

 Different administrative options- DotNetNuke provides you with different administrative options which let you control the website at the host level as well as individual portal level.

These are just some of the benefits of using DotNetNuke websites. There is a whole lot more to this fantastic framework which provides really simplified business solutions. To put it succinctly, DotNetNuke websites are what you should switch to if you are looking to increase your efficiency while keeping the costs to the bare minimum.

With DotNetNuke websites, your small business would no longer lag on the productivity front and you would stand head to head with top notch companies in terms of professionalism and productivity.

Hello,

Your hosting provider should support DotNetNuke requirements as ASP.NET (some of the versions required .NET 4.0) and MS SQL server.

Regards

Yes We support ASP4.0 and all versions of MS Sql Server

Have you tried install the software? had any problems in doing so?

Or you just looking for general tips about it?

I am just looking for is to see how much need is out there for Dotnetnuke hosting and see who all is using it, comments in general about it. I myslef run several sites on it and love the framework.

Well, DotNetNuke is a very solid and famous platform. We have hundreds of users using it and it is extremely popular.

Anyone want to comment on the need for DotNetNuke Hosting?

DNN is certainly getting more popular but I have found that some "shared hosting" solutions just don't cut it for a dotnetnuke installation, or another serious .NET site on the database side of things. I tested DotNetNuke on 2 windows hosting providers (as a student). Default SQL configurations mostly include limited SQL database space. DB logfiles count up really fast and consume the allowed DB space the shared hosting provides in no time, and then the hosting provider does not know how to convert to simple logging or how to prune the logs. As for setting up a non profit site for personal things, and experiencing these kind of troubles quickly sets you back to go to a php alternative that gives no problems to serve the same kind of site with the same kind of volume for much less the money. Paying extra for the windows hosting is ok, but than having to contact hosting multiple times and having to pay extra for database expansion is too much trouble for a personal site. From the moment you start recieving some traffic and your database is 7MB and the logfile of 95 MB exceeds the 100MB limit and the hosting provider does not know how to fix this or it will take multiple support tickets and during the entire support issue your site goes down multiple times... Well you kinda get enough of it, and therefore the need for DNN hosting gets lower as it was higher in the first place.

So I guess what I'm trying to say is that I feel the need is there, but is quickly gone when running into trouble.

I also run a couple of DNN sites and have had some people asking about it. The out of the box funtionality and extendibility is great, but I aint hosting one unless I got a dedicated server at my disposal. So for any personal site I never advise to use DNN, for corperate use where dev time or budget is tight, DNN can be a perfect solution. If you have enough DNN, .NET and SQL knowledge, you shouldn't have too much problems hosting DNN I believe, so you kan keep your customers instead of forcing them to use a php solution.

Other than these experiences I really can't say more about how much request there is for solid DNN hosting.

I also run a couple of DNN sites and have had some people asking about it. The out of the box funtionality and extendibility is great, but I aint hosting one unless I got a dedicated server at my disposal. So for any personal site I never advise to use DNN, for corperate use where dev time or budget is tight, DNN can be a perfect solution. If you have enough DNN, .NET and SQL knowledge, you shouldn't have too much problems hosting DNN I believe, so you kan keep your customers instead of forcing them to use a php solution.

Totally agree with your opinion :agree:

Get something simple for personal site. DNN requires time and effort to fully customize for specific needs.

As a DotnetNuke developer, who've worked with the system for last 2 years, I can tell DotNetNuke is not that complicated... moreover, it is super simple to use it for the content management.

Try some solid dotnetnuke hosting company, e.g. PowerDNN and you shouldn't have any issues. They got auto-setup that makes the setup process seamless.

You have 2 years experience.
People develop personal site would not have any experience and would not know much about html.

From the moment you start recieving some traffic and your database is 7MB and the logfile of 95 MB exceeds the 100MB limit and the hosting provider does not know how to fix this or it will take multiple support tickets and during the entire support issue your site goes down multiple times... Well you kinda get enough of it, and therefore the need for DNN hosting gets lower as it was higher in the first place.

_____
You are correct: DNN log storage can grow quickly if the DNN host has not configured the DNN instance to deal with this including which logs are to be stored.

The log files in this case would be managed by the DNN host - not the host provider of your website. The provider host would look after the server logs. The DNN host would likely look after the DNN logs. Login to your DNN instance as host to deal with your DNN log.


DNN | Host | Host Settings | Other Settings
This is where you can specify Site Log History # Days stored.
This is also where you specify database or file storage.

DNN | Host | Host Settings | Scedule
This is where you can specify Site Log History # Days to purged.

_____
FYI: DNN works very well in a shared hosting environment.


Regards
Mike

DNN is not easy by the definition of "easy" that most people would use. It's resource hungry, and it wants server settings that many hosts would balk at (i.e., dedicated server required). You'll mostly find it in company settings, where IT personnel are hired full-time to develop it and maintain it. A good friend of mine does just this. Even if you have a good bit of SQL and .NET experience, it has a learning curve that would take a few months minimum to fully grasp, and many more months to get it implemented. Don't let experienced programmers make it seem easier than it really is.

DNN is bloatware at its worst. DNN uses a lot of memory resources for little to no reason. I've seen low traffic DNN sites gobble up more than 1GB of RAM. DNN has absolutely no place in shared hosting, since shared hosting means you are willing to share the overall server resources with other small sites. DNN is too bloated to properly share resources.

You can usually build a comparable website using WordPress or Joomla with far fewer server resources.

Hi

I too have seen DotNetNuke use allot of CPU when very little going on, Has anyone ever asked DNN support why this is and do they plan on optimizing it in the future?