Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: Add-on Development.

  1. 09-29-2009, 11:52 PM #1
    imtiyaz is offline Junior Member
    Join Date
    Jun 2009
    Posts
    2

    Post Add-on Development.

    The problem details are being written in the document (Attached).

    Can anyone help ?
    Attached Files Attached Files
  2. 10-09-2009, 09:50 AM #2
    MarkC is offline Developer
    Join Date
    Aug 2006
    Posts
    166

    Default

    The reason you're getting that error is that you're testing it on a separate website, evident on the screenshot. Which bypasses certain initialization stages done on website startup. You may be missing some dlls or web.config entries on your test site. Why not work directly on the aspdnsf site so that you can make sure the proper intitialization steps are taken care of.

    It is always practical to isolate your core logic on a separate project and then just reference that on the web. Though we cannot guarantee that we won't change any code on the signin page from version to version, your requirement seems to be easily accomplished by dropping a textbox on the form and callout the OpenID validation(logic on your separate dll), which doesn't seem to be too much of an upgrade procedure.