Restore DotNetNuke to local development
... on the 8th day of March, 2013
After long time not touch DotNetNuke (DNN), in this time I must touch it. DotNetNuke is a content management system (CMS) for websites, easy to use and highly extensible, with lots of add on modules. It is CMS like Joomla in Open Source, but DNN is written using Asp.net framework.
I must study this stuff again, a zero to hero. Some of them i.e Restore DotNetNuke to local development and upgrade DotNetNuke version to the new one. For restoring DotNetNuke to local development, it is from production for debugging some bugs or problem especially if using third party modules or custom modules. If we do it in production server, very risk. After restoring it, we try to access from browser using localhost URL, it will always redirect to the URL in production server. Very annoying isn’t?
Well, just to the point, step by step are:
- Restore your dnn database to sql server database local, ensure you have account to access to database
- Copy your application files to your local IIS and make a web site and set port, like 80 or others. I recommended to use 80.
- Change database connection in web.config
- Open database that has been restored before, expand database name -> Table -> find table PortalAlias.
- Change or update column HTTPAlias value to your local url name, in this example I set it to “localhost”. Usually the value is domain name in Internet, ex: domain.com. If we don’t change this, it always redirect to domain.com, this is the problem.
- IIS reset
- Access your application in your local server and start for debugging