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 4 of 4

Thread: ADNSF Architecture

  1. #1
    duke is offline Junior Member
    Join Date
    Nov 2009
    Posts
    28

    Smile ADNSF Architecture

    Dear All,

    I am really new in ADNSF. Could some1 please tell me ADNSF architecture document?

    Or any ideas where I should start at?

    Thanks

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    We do not have specific documents like that. what modifications you wanted to achieve? We'll start it from here.

    These tutorial might be helpful:
    http://manual.aspdotnetstorefront.com/p-152-skins.aspx
    http://manual.aspdotnetstorefront.co...intutorial.pdf

  3. #3
    Richnyc30 is offline Senior Member
    Join Date
    Mar 2009
    Posts
    340

    Default Architecture Overview

    1. You have to know XML, XML packages, and CSS. Be sure and look at the CSS file in the skin to know where they use CSS to define things, like the buttons.
    2. Most visual forms are modifiable without having to recompile.
    3. Many things are defined in the skins, but the XML packages are mostly universal.
    4. XML packages, with a bit of modifying, have access to all data.
    5. The pages consist of a template (by skin) and and a XML package include. Modifying the template is not that hard after awhile.
    6. Homepage is setup as a Topic which creates the homepage insert in the template. A useful editor is provided.
    7. It's not easy to use several skins in the same site until you are really experienced. Foretunately this is not an immediate need. Ignore all skins except #1 until later on.
    8. Inventory presentation uses different paradyms than other ecommerce packages. Learn about varients as soon as possible. You only have 2 attributes built in so using the varients is a necessity. It takes a bit of understanding but it has distinct advantages.
    9. Go through the features on www.AspDotNetStorefront.com. It's a long list.
    10. The manual is very basic. Be on the forums like bubble gum on the sidewalk.
    11. Spend time learning the AppConfigs. Learn how to create new categories for the AppConfigs so you can find them again.
    12. Make a Wordpad file with anything you need to remember, like forum posts and AppConfigs.
    13. Topics are important. sometimes it's hard to know if soomething is an AppConfig or topic.
    14. Some third party apps are interesting.
    15. The amount of data entry is staggering. If you thought your previous e-commerce package had lots of product data, you haven't seen ASPDN product entry. Most of them are actually useful. More product images you have the better. Foretunately, the images are auto-resized so you only need a large image.
    16. Good luck. At least you can build a modern e-commerce site with ASPDN.

    Richard

  4. #4
    duke is offline Junior Member
    Join Date
    Nov 2009
    Posts
    28

    Default I need to know how to create simple xml package and compile it as a page

    @Richard: thanks 4 the advice