Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to use new universal installer?How to use new universal installer?
Previous
 
Next
New Post
12/14/2007 12:19 PM
 

Is there any documentation or third-party developer guidance on using the new universal installer introduced in DNN 4.6?

DNN currently uses the new installer system for authentication packages, but according to a Charles Nurse blog entry, the installer is intended to be used for all sorts of things.

I would like to use it for a custom navigation provider (HouseMenu 2). I studied the manifest files for the authentication packages and made a manifest for the menu, but the installer throws a null reference exception. I will walk through and debug this, but I thought I should ask out here for any additional documentation or help.

Tim


--
Tim Rolands
Avastone Technologies | House of Nuke
Where DotNetNuke(R) Lives
 
New Post
12/14/2007 2:20 PM
 

Hi Tim

The Installer was introduced in order to create an Installer for Authentication providers.  It was built in such a way that it could be used to install all sorts of components, and you probably could install a "Provider" today.

However to do that - you would need to register a new "Package Type"  and create the manifest accordingly.

There currently is no documentation - primarily because of time and resources, but also because we are not really ready to open this up fully yet.  This should happen in the first quarter of next year for the initial "Cambrian" release,

To install a provider you would need to build a manifest with a number of components - For example here is the manifest to install the XMLLoggingProvider.

<dotnetnuke type="Package" version="4.0">
    <packages>
        <package name="XMLLoggingProvider" type="Provider" version="02.00.01">
            <description>DotNetNuke XML Logging Provider Project</description>
            <dependencies/>
            <vendor>
                <companyName>DotNetNuke Corporation</companyName>
                <contactInfo>support@dotnetnuke.com</contactInfo>
                <license src="license.txt" />
            </vendor>
            <components>
                <component type="Assembly">
                    <assemblies>
                        <assembly>
                            <path>bin\Providers</path>
                            <name>DotNetNuke.XMLLoggingProvider.dll</name>
                            <version>02.00.01</version>
                        </assembly>
                    </assemblies>
                </component>
                <component type="File">
                    <files>
                        <basePath>Providers\LoggingProviders\XMLLoggingProvider</basePath>
                        <file>
                            <name>license.txt</name>
                        </file>
                    </files>
                </component>
                <component type="Config">
                    <config>
                        <configFile>web.config</configFile>
                        <install>
                            <configuration>
                                <nodes>
                                    <node path="/configuration/dotnetnuke/logging/providers" action="update" key="name" collision="overwrite">
                                        <add name="XMLLoggingProvider" type="DotNetNuke.Services.Log.EventLog.XMLLoggingProvider, DotNetNuke.XMLLoggingProvider"
                                                configfilename="LogConfig.xml.resources" providerPath="~\Providers\LoggingProviders\XMLLoggingProvider\" />
                                    </node>
                                </nodes>
                            </configuration>
                        </install>
                        <uninstall>
                            <configuration>
                                <nodes>
                                    <node path="/configuration/dotnetnuke/logging/providers/add[@name='XMLLoggingProvider']" action="remove" />
                                </nodes>
                            </configuration>
                        </uninstall>
                    </config>
                </component>
                <component type="Cleanup">
                    <files>
                        <file>
                            <path>bin</path>
                            <name>DotNetNuke.XMLLoggingProvider.dll</name>
                        </file>
                    </files>
                </component>
            </components>
        </package>
    </packages>
</dotnetnuke>

This has an "Assembly" component to install the assembly, a "Files" component to copy the license.txt file, a "Config" component to update the web.config file and a "CleanUp" component to remove the old version of the provider (the "Assembly" component nistalls the assembly into bin\Providers so the old assembly in /bin needs to be removed.

As long as you follow this approach - it should work today - you would need to add the provider Package type to the PackageTypes table.

Anyway, while this should help you - the final API has not been ironed out yet, so ther may be changes once the Installer is fully implemented.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
12/17/2007 3:13 PM
 

Charles,

Thanks so much for the informative reply. I guess I'll just hold off for now and stick with the manual installation instructions.

Tim


--
Tim Rolands
Avastone Technologies | House of Nuke
Where DotNetNuke(R) Lives
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to use new universal installer?How to use new universal installer?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out