Utility :: Installer

DotNetNuke Windows Installer Makes its Debut!

Antonio Chagoury — Fri, 09 Mar 2007 21:55:00 GMT

The DotNetNuke Windows Installer was released and made available for download today. To get your own copy of the Installer visit the project or donwloads page.

This version installs DotNetNuke 4.4.1.

We are already working on the next release, 4.5. The next release will host a few minor changes to the UI as we work on improving the user experience.

As usual, your feedback is appreciated.

DotNetNuke 4.4.1 Installer Beta

Antonio Chagoury — Wed, 14 Feb 2007 19:48:00 GMT

I wanted to announce that I have just finished packaging the DotNetNuke Install Utility for version 4.4.1.

I am now looking for Beta Testers (A.K.A Guinea Pigs), so please contact me if you are interested in taking it for a spin.

While I work on the next generation of the installer I will continue to package every new release of DotNetNuke in the current format - which is already great!

Please post any issues related to the installer on the project forum and/or the Issue Log.

Thanks and enjoy your Valentine's day!

Installer Project: Roadmap

Antonio Chagoury — Wed, 10 Jan 2007 04:14:00 GMT

I wanted to take some time to share my thoughts on the the future on the Installer project as well as the ideas I have for improving the current product.

First, I will define what I feel is the scope of the installer as follows:

"An installation utility which enables IT and IT-less individuals alike to set-up or upgrade a DotNetNuke portal with 0 technical skill and knowlegde."

Or as Geico would put it: "Even a cave-man can do it!"

Now that we've defined our target goal, let's dig down to the "nuts and bolts".

The current implementation of the Installer is built using an installation software program such as InstallShield. In fact, I believe it was built with InnoSetup, a free utility.
Based on my past experiences I can say that using these kinds of utilities require a high learning curve, and limits the end user's experience because of their lack of functionality.
To start off, many of these utilities require you to learn a whole new programming language. Most have their own implementations that consist of coktails of C, and VB.

So, instead of re-inventing the wheel, the new installer will be built with a language that I know well (VB.net) and on a platform on which DotNetNuke requires in order to function (.net), and will be in the form and a Windows Application.
Needless to say, by taking this route we stand to benefit a great deal in terms of UI, UX and functionality, without having to learn a whole new language and without the dependance on third party tools.

The project is currently in full motion. To be more specific, I have started (and finished) the Wizard Control of the installer as well as the main installer API (more on this on my next blog post).

For those of you reading this post, now is a good time to submit your ideas, comments, and suggestions, and I am looking forward to receiving them.
I would appreciate it if you post your suggestions on either the Forums or directly in the Issue Log.