I installed DotNetNuke at least four times from the packaged .ZIP, but it was several weeks and while I installed it from the .ZIP today for a virgin scratch site to test my home-made DNN modules I realized I forgot most of the process. So this is a review to get DNN working quickly in development.
- First thing is to unzip the package into a website subdirectory.
- Update the unzipped dotnetnuke.sln and .webinfo files to reflect the url location for the app
- Go into IIS and configure the directory as an application
- Create a SQL database. Be sure the SQL user account accessing the database is owner.
- Double click on the dotnetnuke.proj file. The new DotNetNuke VS.NET project should open without squawking at all.
- Update the web.config, changing the default AccessDataProvider to SqlDataProvider and complete the DataProvider connection info. CasE SensiTive. Entering SQLDataProvider will generate a runtime.
Funny. It was here that I was stuck and had forgotten completely how to load the SQL Database script to build the database. I was looking through the directories when it hit me that all I had to do at this point was fire up the new DNN site and it would know to run the database object setup script automatically.
Done. Now, time to see if the first DNN Module PA Install ZIP I created today will install correctly....