Archive
Monthly
Go
|
|
DNN Blog
Feb
1
Posted by:
Charles Nurse
2/1/2008
In my previous Blog I introduced the new Features Modules which will be part of the initial Cambrian release. This module consolidates the management of all DotNetNuke extensions (or Features). In this blog I will show the new installer at work.
As with the Module Definitions module the new Features module includes an Action that allows you to Install a new Feature.
If you clcik on the "Install New Feature" action you will launch the new "Install" wizard. This wizard was introduced in v4.6 as a means of installing the new Authentication Services, but is now used for all Features.
In this first screen which is similar to the old Module/Skin upload page you can use the browse button to locate the package you want to install. When you have located it click next to proceed to the next step. Note. When you click Next the zip package is unzipped to a temporary location and the manifest file is loaded. If there are any errors, a log will displayed and you will not be able to continue.
The next step in the Wizard displays the information about the package. In this example I am installing the default DNN-Blue Skin package. The information on this screen has not been finalised yet. For example we will probably add the ability for developers to include Company/Contact information.
The third screen in the Wizard will display the Release Notes for the Package. What is included here is entirely at the discretion of the developer, but in the example of a DotnetNuke Module project the relesae notes could be the list of Gemini issues fixed.
The fourth screen in the Wizard displays the License (EULA) and requires the user to accept the license.
Note - if you click Next without accepting the license the "red" Validation text will be displayed.
Finally when you click the Next button the package will install and the Installation Log will be displayed.
Note. In this example the log was so long that I have just dispaayed the top and the bottom of the screen.
The same process will happen whatever feature you install. In the next part of this series I will dive more into the mechanics of the new "Feature" system.
17 comment(s) so far...
Re: Cambrian First Look - New Features Module (Pt 2)
I have a stupid question. What does the [L] mean?
By ahawes on
2/1/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Very cool, the Cambrian release looks like it will be quite an improvement over previous versions.
ahawes: The [L] is displayed when using in the web.config. It allows you to see if there are any missing localization keys.
By Zacki2 on
2/1/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Oops, I copied and pasted the key from the web.config file, and when I submitted it was removed. It's the ShowMissingKeys key in the web.config. More info here: http://www.dotnetnuke.com/LinkClick.aspx?fileticket=4235no3DZfU%3D&tabid=478&mid=857
By Zacki2 on
2/1/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
This new installer looks great for packages/modules but, the current installer has always worked pretty well. Are you considering a similar installer for DNN Core Releases. Upgrading existing core installations is much more difficult currently.
By bbuell on
2/1/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
If there is a dependancy issue (i.e. feature requires minimum version of DNN but current version is prior to that) how does that show up?
By lneville on
2/1/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
This looks very interesting, may I request that on one of the installation pages we have the option to mark the module/feature as 'premium' on installation?
Similarly, can the modules page have a column that shows whether module is premium or not please (maybe next to the pencil)?
Many thanks
Barry
By BarryS on
2/2/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
This does look good. Would it be possible for Version info to allow the developer to include data like "Beta 1" and "RC1". Right now, such versions always appear as normal release versions so it is difficult to know what is installed. I suppose the Release notes could be used for this, but that info would not be visible on the main page. Thanks.
By rralston on
2/2/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Great stuff. I assume the installation gets logged to a text or xml file somewhere? Would it be possible to include a clickable hyperlink below "Installation successful" or "failed"...
e.g.
"This installation was logged here for future reference: http://www.dotnetnuke.com/DNNBlueSkin-install-mm/dd/yyyy.log
Just a thought anyway.....
By NukeAlexS on
2/2/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Good ideas - as we are not at code freeze yet - we will keep them in mind.
The reason for a new Installer was that the previous 3 installers Module/Skin/Languages all had custom installation code. In order to fulfil one of the Cambrian goals - making the App more extensible/flexible - it was decided that building a single unified (and extensible) approach to Installing/Managing/Uninstalling/Package Creation would be neccessary - and much more maintainable moving forward, as functions used by all features are now extracted into a single place.
More on the design in future Parts.
By cnurse on
2/2/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Very cool updated.
Before knowing about this project, I had posted a feature request: http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6995&PROJID=2
Which would fit into your project perfectly, it is the idea of simply allowing some custom catigorization of the modules so that we can easily manage what we have installed.
Anyhow I see you have designed a nice structure for organzing things, I"m curious if the idea of end user organization will be available as noted in the feature request?
Thanks for all your hard work on this project! I hope to gain enough knowledge to help this community grow, and show my appreciation.
Josh
By chicagojsh on
2/4/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
BTW ignore the fact that I can't spell :->
By chicagojsh on
2/4/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
What does the developer need to do in order to have the above License Text (must accept) appear ?
Also, what will happen, if someone trys to add an old Install package (may be dnn 3.x) on this new dnn installation ?
By IndianGuru on
2/6/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
I am assuming that this is a "Host" only function or will a similar model be available for admins installing skins, containers, and adjusting Authentication settings?
By simonduz on
2/11/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
I am assuming that this is a "Host" only function or will a similar model be available for admins installing skins, containers, and adjusting Authentication settings?
By simonduz on
2/11/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
All great ideas, and these Cambrian updates are so EXCITING! I especially like the suggestion by NukeAlexS.
By hismightiness on
2/12/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
In the 2nd comment there was the following comment "The [L] is displayed when using in the web.config. It allows you to see if there are any missing localization keys."
I have set the ShowMissingKeys tag to True in my Web.config and sure enough I am seeing the [L] in places. Does this mean that these places are missing localisation keys or that they are correct?
By SupaHoopsa on
2/14/2008
|
Re: Cambrian First Look - New Features Module (Pt 2)
Charles - Will consideration be placed on actually documenting the new structure(s) for .dnn files for installing the packages? As a module developer that is a big concern that I have, as trying to figure out how to install my first custom authentication provider was much more involved than it should have been.
This change to the structure of module installations etc looks awesome and I can't wait to try it out as it can REALLY simply the user interface for my clients.
By mitchel.sellers@gmail.com on
2/27/2008
|
|