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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsProvidersProvidersProvider Packages in manifest fileProvider Packages in manifest file
Previous
 
Next
New Post
6/2/2012 3:05 AM
 

There is a remote possibility that my problem here is related to the one in the previous message. Anyway, this one is about the same Sitemap Provider, but this one is about the syntax of the manifest file.

My manifest file now contains 3 packages (when finished and ready for publication, it should contain 4). 2 of those are of the type="Module" and without the 3rd package, they install without problem. The 3rd package is of the type "Provider". Nowhere from the documentation could I conclude clearly if this type is apropriate for this purpose. The package has the customary heading nodes (friendly name, description, owner, release notes, licence and dependencies.

The components section has 2 components, one of the Config and one of the Assembly type. Without the Config component, the manifest installs without complaining. It is the config component that blocks the installation:<component type="Config">
          <configFile>web.config</configFile>
          <install>
            <configuration>
              <nodes>
                <node path="/configuration/dotnetnuke/sitemap/providers" action="update" key="name" collision="overwrite">
                  <add name="KhmerSupportNewsDeskSiteMapProvider" type="KhmerSupport.Providers.NewsDesk.Sitemap, KhmerSupport.NewsDesk"
                       providerPath="~\DesktopModules\KhmerSupport.NewsDesk\Providers\SitemapProvider\KhmerSupport.NewsDesk.SitemapProvider\" />
                </node>
              </nodes>
            </configuration>
          </install>
          <uninstall>
            <configuration>
              <nodes>
                <node path="/configuration/dotnetnuke/sitemap/providers/add[@name='KhmerSupportNewsDeskSiteMapProvider']" action="remove" />
              </nodes>
            </configuration>
          </uninstall>
        </component>

I've tried replacing both nodes with <node />,  it still did not install.

In the event viewer, I find this explanation for the error:

InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Services.Installer.Installers.ConfigInstaller.ReadManifest
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at
DotNetNuke.Services.Installer.Installers.ConfigInstaller.ReadManifest(XPathNavigator manifestNav) at
DotNetNuke.Services.Installer.Installers.InstallerFactory.GetInstaller(XPathNavigator manifestNav, PackageInfo package) at
DotNetNuke.Services.Installer.Installers.PackageInstaller.ReadComponents(XPathNavigator manifestNav) at
DotNetNuke.Services.Installer.Installers.PackageInstaller.ReadManifest(XPathNavigator manifestNav) at
DotNetNuke.Services.Installer.Installers.PackageInstaller..ctor(String packageManifest, InstallerInfo info) at
DotNetNuke.Services.Installer.Installer.ProcessPackages(XPathNavigator rootNav) at DotNetNuke.Services.Installer.Installer.ReadManifest
(Stream stream) at DotNetNuke.Services.Installer.Installer.ReadManifest(Boolean deleteTemp) at
DotNetNuke.Modules.Admin.Extensions.Install.wizInstall_NextButtonClick(Object sender, WizardNavigationEventArgs e) at
System.Web.UI.WebControls.Wizard.OnNextButtonClick(WizardNavigationEventArgs e) at
System.Web.UI.WebControls.Wizard.OnBubbleEvent(Object source, EventArgs e) at
System.Web.UI.WebControls.Wizard.WizardChildTable.OnBubbleEvent(Object source, EventArgs args) at
System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) at System.Web.UI.WebControls.LinkButton.OnCommand
(CommandEventArgs e) at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Adding the provider in web.config did make the provider appear in dnn's Sitemap Provider Module's provider table but not under Providers on Admin>Extensions. Is that necessary or required? Would one not need that for uninstallation? The component type="Provider" does not have any effect thereto according to what I read here.

So what am I overlooking?


____________________________________
The one-eyed in the land of the blind.
 
New Post
7/13/2012 1:07 AM
 

This one I solved by running the setup on a clean setup of the source.

There was a config tag missing right after the tag component type="config" before the configfile tag

 


____________________________________
The one-eyed in the land of the blind.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsProvidersProvidersProvider Packages in manifest fileProvider Packages in manifest file


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