Results 1 to 4 of 4

Thread: Location of XML Config File

  1. #1
    Join Date
    Apr 2012
    Posts
    165

    Default Location of XML Config File

    Hi

    I raised this with support but thought I would try here as well.

    I cloned our product's xml package to use to display discontinued products. On this page a pop up box was added displaying the discontinued products related products. I had to re-design the relatedproducts.xml.config file especially for this page. This relatedproducts.xml.config file sits within the App_Templates/XmlPackages folder.

    I want the standard product's xml package (not discontinued) to use the relatedproducts.xml.config file that sits within the web/XMLPackages file. Yet when I try this I get a message saying

    Extension object 'urn:aspdnsf' does not contain a matching....

    Any idea how I can point the products xml package to the relatedproducts.xml.config file in the web root folder?

    Thanks

  2. #2
    Join Date
    Apr 2012
    Posts
    165

    Default

    Ok so basically I am trying to run the xml package twice on the page but using different names. Here is the error I am getting? Any thoughts?

    Page URL:/p-51932-morepa-chewable-orange-60-softgels.aspx
    Source:System.Data.SqlXml
    Message:Extension object 'urn:aspdnsf' does not contain a matching 'RelatedProductsorig' method that has 1 parameter(s).
    Stack Trace:
    at System.Xml.Xsl.Runtime.XmlExtensionFunction.Bind()
    at System.Xml.Xsl.Runtime.XmlExtensionFunctionTable.B ind(String name, String namespaceUri, Int32 numArgs, Type objectType, BindingFlags flags)
    at System.Xml.Xsl.Runtime.XmlQueryContext.InvokeXsltL ateBoundFunction(String name, String namespaceUri, IList`1[] args)
    at <xsl:template match="Product">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, IList`1 pName, IList`1 mID, IList`1 mSE, IList`1 mName, IList`1 pDescription, IList`1 ProdSize, IList`1 pSalesPromptName, XPathNavigator AltText, XPathNavigator ManURL)
    at <xsl:apply-templates>(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator )
    at <xsl:template match="/">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current)
    at Root(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
    at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter writer, Boolean closeWriter)
    at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigabl e contextDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter results)
    at System.Xml.Xsl.XslCompiledTransform.Transform(IXPa thNavigable input, XsltArgumentList arguments, Stream results)
    at AspDotNetStorefrontCore.XmlPackage2.TransformStrin g()

    Any ideas on how I can use the original and modified xml file on the product page using different names?

  3. #3
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Is that message word for word exactly what you're getting?

    Message:Extension object 'urn:aspdnsf' does not contain a matching 'RelatedProductsorig' method that has 1 parameter(s).
    ...cause there's no method called "RelatedProductsorig". That looks like a simple typo somewhere in your XML package.

  4. #4
    Join Date
    Apr 2012
    Posts
    165

    Default

    Hi

    It's ok got it sorted in the end.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •