|
|
SINCE 1995, We offer what developers want and need:
Source code (for ML, ML/DNN, or IS versions) optionally available in C# or VB.NET
- Asp.net 2.0
- MS-SQL 2000/2005 supported
- Visual Studio.net 2005 supported
- Integration with industry leading asp.net menu, tree, and site map controls from ComponentArt
- Ability to design skins in Dreamweaver or FrontPage
- Excel or Xml product import
- Support for most popular gateways: Authorize.net, Verisign, Linkpoint, PayPal, PayPal Express, PayPal Website Payments PRO, Google Checkout, and dozens more
- COMPLETE, and we mean complete, support for robust Search Engine crawling, with full control over static page links, and complete control over all meta tags, titles, keywords, descriptions, alt-text, noscript blocks on EACH and EVERY product and category in the storefront! Some larger sites we know have over 350,000 pages fully indexed in Google!
- RealTime FedEx, UPS, DHL, USPS, and Canada Post Shipping Rates already integrated. Canada Post supported only in ML version currently
- Minimum quantities, restricted products, password protected topics, support for up to 1000 HTML type content pages, affiliate tracking through to customer and order records, recurring items, download products, subscription items, custom address book, easy one button re-order, auto image watermarking, and more
NO limits on # of products, database size, etc. Up to 2000 categories, departments, with nesting to any level.
- Highly optimized entity and object XmlHierarchy objects supporting nested table structures
- XmlPackages (Patent Pending) allowing total data-drive Xml/Xslt control over page rendering
- Ability to support user controls
- Ability for you to add new pages to our solutions
- Over 50 class objects (View Class Diagram)
- Powerful Skinning Engine
- Robust feature set for truly minimal cost, to jump start your
projects for your clients: wish lists, Google site maps, Yahoo!
site maps, Froogle support, Skinning
Engine, Xml/Xslt rendering engine, gift registry, customer
levels, quantity discounts, coupons, multi-lingual support, and
HUNDREDS of other features...you generally find these features
only carts that cost upwards of $2000 or more!
- Integrated .NET Forms Authentication
- Host on your server, or just about any Windows NT hosting company
- No tricks or gimmicks. Just a solid platform to develop with.
- Multiple license discounts available.
"I tried Sales.Cart (ComCity), BVCommerce, Storefront 6.0 (Lagarde)
and settled on AspDotNetStorefront PRO. I had a very bad
experience with both Sales.Cart and StoreFront. These guys
say they offer a 30 day money back guarantee, but in the
fine print they don't offer this on the web hosting, or
support so I really had to fight hard to get my money back
after trying their solution for less than a week.
I'm glad I didn't settle for that, because I have much
more control over my pages and the data with the
AspDotNetStorefront solution. I've had to learn SQL and .NET
a little bit more than I knew already, but these other carts
mask you from what's going on with your data. So now my site
is live and I know it backwards and forwards.
The other most important thing for me was support.
AspDotNetStorefront has been incredible. It seems they are
always around, which is great since I seem to always be
working on my site. It seems I never have to wait more than
a couple of hours to get an answer from them.
Per their recommendation I went with EDTHosting. Having
started a hosting business in the past I am really impressed
by their operations and their support. They seem to share
the same support credo as AspDotNetStorefront - Always
around and have a solution within hours.
All in all I am a very happy camper. And, if you add all
of it together (the hosting and AspDotNetStorefront ) it's
still cheaper by 20% - 40% than these other guys. And I feel
I'm getting a much better solution.
At that time I was trying to get my over $2K back from the
other cart guys after nothing worked. After a few days I got the new AspDotNetStorefront site up and was in business. Thanks AspDotNetStorefront."
- Joseph C. Loll, ZUP
NOTE: VB.NET source only available with ML, ML/DNN, and IS versions purchased with optional full source.
Full source code is optionally available for AspDotNetStorefront ML, ML/DNN and IS versions. This allows you to fully customize storefront features to match exacting client requirements. We realize that every online business has their own unique business rules, which you have to accomodate. Stop settling for cookie cutter storefront solutions which offer no ability for customization or not flexibility. When optionally purchased, source code is provided in asp.net 2.0 format, in either C# or VB.NET languages, with full SQL database schema. Visual Studio.net 2005 is supported and full project and solution files are provided.
The only source that we do not provide, and you should never need is:
a) the source for our encrypt dll, and
b) source for any third party controls (e.g. ComponentArt menus) that are used in the storefront.
It is almost never needed to have the encrypt dll source, and we provide a Security.cs (Security.vb) class wrapper for it, in case you do have to provide/utilize your own encryption routines.
We treat developers like developers...no tricks or gimmicks. Just a solid platform to develop on.
Multiple license discounts available.
"I tried Sales.Cart (ComCity), BVCommerce, Storefront 6.0 (Lagarde)
and settled on AspDotNetStorefront PRO. I had a very bad
experience with both Sales.Cart and StoreFront. These guys
say they offer a 30 day money back guarantee, but in the
fine print they don't offer this on the web hosting, or
support so I really had to fight hard to get my money back
after trying their solution for less than a week.
I'm glad I didn't settle for that, because I have much
more control over my pages and the data with the
AspDotNetStorefront solution. I've had to learn SQL and .NET
a little bit more than I knew already, but these other carts
mask you from what's going on with your data. So now my site
is live and I know it backwards and forwards.
The other most important thing for me was support.
AspDotNetStorefront has been incredible. It seems they are
always around, which is great since I seem to always be
working on my site. It seems I never have to wait more than
a couple of hours to get an answer from them.
Per their recommendation I went with EDTHosting. Having
started a hosting business in the past I am really impressed
by their operations and their support. They seem to share
the same support credo as AspDotNetStorefront - Always
around and have a solution within hours.
All in all I am a very happy camper. And, if you add all
of it together (the hosting and AspDotNetStorefront ) it's
still cheaper by 20% - 40% than these other guys. And I feel
I'm getting a much better solution.
At that time I was trying to get over $2K back from the
other cart guys and here AspDotNetStorefront sent me the
actual full product prior to the sale. I thought these guys
have balls (excuse the expression) about there solution.
After a few days I got the site to work and sent them the
money. "
- Joseph C. Loll, ZUP
We provide over 25 class objects that you can build on and customize or leverage.
View as PDF
SAMPLE C# CODE FRAGMENTS
SAMPLE VB.NET CODE FRAGMENTS
NOTE: VB.NET source only available with ML, ML/DNN, and IS versions purchased with optional full source.
SAMPLE SQL STORED PROCS & TABLE FRAGMENTS (We support SQL 2000 or SQL 2005)
XmlPackage Overview & Operation (Patent Pending)
XmlPackages are a means by which developers can extend the functionality of
AspDotNetStorefront without necessarily having to know asp.net and/or recompile the storefront. One great example is adding a new "shopping site" feed...you don't have to recompile the storefront, you can simply write a new "feed" XmlPackage that generates the shopping comparision site feed data easily, and add this XmlPackage to your admin site. This allows developers to add features easily wihtout rebuilding the core source or waiting for us to add the feature.
XmlPackages also provide a middle-tier layer which separates business logic (code) from presentation layer (html), and allows the XmlPackage to bring those two areas together without mixing HTML into your code objects
The storefront uses XmlPackages to render ALL category, manufacturer, department, and product pages. This allows you to easily add completely new page layouts to the storefront just by wrting a new XmlPackage! The storefront also uses XmlPackages for all customer notifications, including Receipts, Your Order Has Shipped, Distributor Drop Ship Notifications, etc...so you can also completely customize these messages.
A knowledge of Xml, Xsl (Xslt), and SQL is required to fully utilize XmlPackages.
XmlPackages have two purposes:
- Internal Packages: these are used internally by AspDotNetStorefront to provide efficient
access to nested entity (e.g. category, section, library, etc) and object (e.g. product,
document) structures in the database. The storefront will NOT function if these
XmlPackages removed.
- Display Rendering Packages: These XmlPackages are created by third party developers
(anyone really) to allow generation of custom page HTML output for entity and/or object
pages. An example is to create a custom category page display format for the storefront.
What is an XmlPackage?
Conceptually, an XmlPackage is pretty simple: they take an input data set or data sets
(or SQL statement, or web service call) and combines that data with automatically generated system and customer run-time environmental data (e.g. query string params, form params, cookies, etc), and then
produces some output document. The output document can be almost any format, but the most common are: Xml for structured data or HTML for web page display content.
XmlPackages are named with the .web.config extension (e.g. MyXmlPackage1.web.config).
The steps by which an XmlPackage performs it's magic is as follows:
- Package is instantiated by Name (the filename, e.g. MyXmlPackage1.web.config)
- Package reads .xml.config file
- Code adds additional run-time parameters to the XmlPackage
- Code adds additional system defined parameters to the XmlPackage
- DataSets are built from the SQL statements
- DataSets are converted into XmlDocument
- XmlDocument is Xsl Transformed into final Xml or HTML. You can even have multiple transforms in one XmlPackage
- Caller of Package will typically then process any AspDotNetStorefront specific tokens in the output (if HTML) and render it on the page
XmlPackages are defined by the XSLT language. The technologies of: Xml, Xsl, SQL, HTML,
XHTML, etc are all leveraged to write effective XmlPackages. There are many tutorials
and good books on those technologies, so they are not discussed here, except where any unusual
exceptions or requirements are imposed by the storefront.
Please remember that XmlPackages are XHTML compliant.
Internal XmlPackages
When used internally as a helper object, the XmlPackage typically produces an in-memory
XmlDocument object, as a result of input SQL statements, and various customer, system, and
userdefined parameters. Examples of these internal packages can be found by looking at files
such as:
- /XmlPackages/CategoryMgr.xml.config
- /XmlPackages/ManufacturerMgr.xml.config
- etc...
This manual does not describe in further detail how the XmlPackages are internally used by the
storefront for managing entities. You can refer to the EntityHelper.cs, and
HierarchicalTableMgr.cs classes in the common project, and the ShowEntityPage.cs class in the
storefront project. Various consumer pages of these objects include the SiteMap.cs classes, and
the SiteMapComponentArt.cs classes.
Display Rendering XmlPackages
When used by developers or customers, this type of XmlPackage outputs HTML to be
rendered within a store page, typically rendering within the skin in the contents area.
We now discuss how users can add new XmlPackages to the storefront WITHOUT recompiling
any code in the storefront. This is important to allow developers to add custom page formats for
their clients. For example, a particular store client may want their category pages to be displayed
in a certain manner, which is not one of the built-in provided formats of the software. The
developer can then author an XmlPackage (in notepad if required), copy that XmlPackage to the
server, and tell the storefront to use that XmlPackage to render the specified category(ies) via the
Admin site.
Installing XmlPackages
XmlPackages are installed by placing them in XmlPackages folder in the web site or in
/admin/XmlPackages. XmlPackage requirements may differ if they are used on the store site vs.
the admin site. XmlPackages can also be stored by skin in skins/skin_1/XmlPackages,
because different skin layouts may require different manifestations of the package.
When your XmlPackage is ready for use, just FTP copy the file into that directory.
Then, you can assign that XmlPackage to any category, section, manufacturer, library, product,
or document in the storefront using the Admin site. When editing these pages in the Admin panel,
you will now select the Display Format of XmlPackage in the select list, and then pick which
XmlPackage file is to be used in the Xml Package select list as shown below:
When the display format of XmlPackage is chosen for your page, your XmlPackage is solely
responsible for producing the output from that page's contents areas! This gives you
COMPLETE control over what is rendered within the skin content area.
Invoking XmlPackages By Themselves
The new page engine.aspx?xmlpackage=XXXXXX has also been added to the storefront. The
static URL shorthand for this is e-XXXXXX.aspx.
This new engine page now allows you to do things using dynamic data to add totally new
pages in your store. For example, suppose you want to have a page which lists the top 5
most heavily discounted products in your db. You can now write an XmlPackage to do that,
and link to it from your skin. Suppose you need a page which lists the most 25 recently
added products in the store, you can write an XmlPackage to do that. And with both
packages, you have full control over the data that is being used to generate the page, and
the display format used to render the page results. All this is possible by writing .xslt files
with the necessary XmlPackage instructions. No change to the asp.net storefront code is
required. To deploy a new XmlPackage page to your site, all you have to do is FTP the
XmlPackage file to the /XmlPackages directory of your web server and invoke it
(presumably after you have tested and debugged it on your development server).
Full real-time Debugging & Breakpoints in XmlPackages
You can set AppConfig:Xml.DumpTransform=true, and the XmlPackage engine will write
intermediate .xml files into the /image directory (they are put here because the site already has
write permissions to that folder). The xml files will be appropriately named based on the name of
the xml package, and also intermediate stage files will be written out.
To debug your xsl transforms, you can use your favorite Xsl debugger tool or Visual Studio.net directly
Example XmlPackage
The following XmlPackage shows an example of how to display a category (entity) page in grid icon layout..and shows how easy it would be to alter this layout, as the XmlPackage separates structure (html) from content (database information)
For more information, see our XmlPackage Specification document in the manual
The following Platinum DevNet partners have experience in creating and deploying customized AspDotNetStorefront projects for clients. If your e-commerce project involves custom and/or unique business requirements, they could assist with your project.
 Misakko, Inc.
                                 
+
|
 |
 Misakko, Inc.
Contact: Harrison (Xi) Lu
Phone: (800)-920-7811
EMail:
Web: http://www.misakko.com
| Project Types Accepted |
|
| ML: |
 |
| ML/DNN: |
 |
| IS eBusiness: |
 |
| Skin Design: |
 |
|
 |
Misakko Inc. provides design and customization services for AspDotNetStorefront. They have been working with the product since version 3.8 PRO in 2004 (now on 5.x/6.x/7.x C#/VB) and can walk you through all aspects of doing business online using AspDotNetStorefront- including graphic design, skin implementation, function customization, search engine optimization, order fulfillment and third party integration.
Mr. Lu has extensive experiences in E-Commerce and has worked as Sr. Consultant for Microsoft, Verizon and MCI on large scale E-commerce projects. Mr. Lu has certifications from Oracle (OCP), Microsoft (MCDBA), Sun Microsystems (SCSA), and ISC2 (CISSP). He also holds MBA/MS degree in E-Business from Temple University.
Sample Sites at http://www.misakko.com/case-study-c1.aspx
For more information about this DevNet partner, click here.
|
 Vortx, Inc.
                                 
+
|
 |
 Vortx, Inc.
Contact: Jo Stewart
Phone: 541.201.9965
EMail:
Web: http://www.vortx.com
| Project Types Accepted |
|
| ML: |
 |
| ML/DNN: |
 |
| IS eBusiness: |
 |
| Skin Design: |
 |
|
 |
Vortx is delighted to provide customization and design services for the AspDotNetStorefront platform.
We bring a range of expertise to each project, whether to customers just starting out or to fortune 500 companies requiring enterprise-level solutions.
- Customizations
- Creative design, layout, navigation, skinning
- Back-office integration
- Data migration and product import
- Search Engine Optimization
- Permission-based email marketing
- Blog, social networking, and viral marketing
- A/B and multivariate testing
- Database and performance tuning
- Hosting and data center services
We are passionate about providing excellent customer service, and we believe service starts with a "teaming" attitude.
We are professional, approachable, and always commit to work within an agreed time and budget.
For more information about this DevNet partner, click here.
|
 Compunix, LLC.
                             |
 |
 Compunix, LLC.
Contact: Jan Simacek
Phone: 623-434-2121
EMail:
Web: http://www.compunix.us
| Project Types Accepted |
|
| ML: |
 |
| ML/DNN: |
|
| IS eBusiness: |
 |
| Skin Design: |
 |
|
 |
Compunix, LLC, being located in Phoenix, Arizona, works closely with the AspDotNetStorefront team. Specializing in Web/Windows Client enterprise applications, eCommerce solutions and Embedded Systems development, we have over 18 years of professional experience giving us the edge to tackle the most difficult of projects that are cross platform, cross tier and cross applications.
We have a dedicated team for custom AspDotNetStorefront cart development and have developed on all versions (4.x, 5.9.x, 6.x, 7.x) of AspDotNetStorefront.
Our extensive list of modification projects using the AspDotNetStorefront platform are within but not limited:
- Existing Windows/Legacy systems and accounting software integration using windows agents and services to synchronize customer and order data:
- MAS90
- Advantage
- Shopatron
- Others
- Dynamic document/preview generation for orders:
- Custom PDF forms
- Word documents
- Order based images and forms
- Customer profiles and community suites to add a social aspect to the cart
- Site-wide smart navigation, filters and search for the unique operations your business models require
- Email and campaign management consoles
- Data management and custom exports
- Custom skin integrations and XmlPackages
For more information about this DevNet partner, click here.
|
 Impact Direct
          |
 |
 Impact Direct
Contact: Ash Sayani
Phone: 800-920-3616
EMail:
Web: http://www.impact-direct.com
| Project Types Accepted |
|
| ML: |
 |
| ML/DNN: |
|
| IS eBusiness: |
 |
| Skin Design: |
 |
|
 |
IMPACT-DIRECT with offices in New Jersey and Alberta, provides full service Ecommerce and SEO solutions. We take care of everything, so you can concentrate on your business: Site design, Skin design and implementation, Search Engine Optimization, Premium Hosting, internet gateway and merchant account setup, and of course your Aspdotnetstorefront shopping cart.
With clients in California, Texas, Arizona, Florida, New York and almost every State in between as well as New Zealand, Canada and Italy, we are a multi-national firm with a diversified client and industry base.
Impact-Direct can help develop your ecommerce site, brand your company, increase your rankings, drive traffic and improve your conversions. Rather than attempting to coordinate several third party vendors which can be time consuming and inefficient, develop a partnership with a single source provider.
Impact-Direct is a dedicated team of professionals who commit the time, knowledge and resources to develop your Aspdotnetstorefront site and keep your business ahead of the competition.
Call us for your upcoming project, 1-800-920-3616.
For more information about this DevNet partner, click here.
|
DEVNET TERMS & CONDITIONS
- The companies listed are independent vendors.
- Billing for all products and/or services is between the vendor and you (the customer) directly.
- Terms & conditions, features, and pricing of product/service/customizations subject to change. Please review each vendor's site for terms of service, services offerred, billing rates, and limitations and contract/service requirements.
- Technical support for all customizations performed are provided by the vendors themselves.
- Use of any DevNet partner to perform product customization requires a valid AspDotNetStorefront license. DevNet partners are prohibited from performing customizations which violate our end user license agreement or source license agreement
- AspDotNetStorefront assumes no responsibility with regard to the selection, performance or use of the companies listed on this page. Any listing of third party companies, developers, consultants, translators, products and services is for informational purposes only and constitutes neither an endorsement nor a recommendation. All understandings, agreements or warranties, if any, take place directly between the vendors and prospective users.
Skinning Allows Site Customization Without Source Code
A "skin" is the means by which you can fully customize the appearance of your web site, and in nearly all cases, you can do it without requiring source code or other asp.net code changes.
Conceptually, a skin is very simple, it's a set of HTML file(s), CSS style sheets, and graphics, that the storefront uses to generate the overall appearance of your storefront.
For developers, even when using skins, you can still design and add any custom pages to the AspDotNetStorefront solution using traditional asp.net web forms, user controls, and other techniques which are standard. They just appear "inside" the site skin by "magic" when rendered by our Skinning Engine
Skins are VITAL to the success of your business...after all, it IS your brand appearance and presentation to customers that will drive the most in revenue growth and conversion rates
You almost never need source code to do "skinning" in AspDotNetStorefront.
Additionaly, you can almost always create a skin from your existing web site or design, by following a very simple procedure outlined in our skinning tutorial manual section.
Skins can also be created initially in FrontPage, DreamWeaver, Expressions Web Editor, or any other HTML design tool that you, or your designer, prefers!
Stop settling for a cookie-cutter site that looks like hundreds of other sites...with AspDotNetStorefront, you can take control of your site's appearance and presentation, so it's how YOU want it to be
You can even have multiple skins per store, and even multiple templates per skin, so you could have your "Shoes" category with one appearance and your "Dresses" category with a completely separate appearance. There is almost no restrictions on what you are allowed to do in skins. Any valid HTML, XHTML, Flash or other components can be used! You can also even vary skins by affiliate id's, so customers from your "Affiliate A" see skin 1 and customers from your "Affiliate B" see skin 2!
Just look at the wide array of designs that are possible in AspDotNetStorefront:

For more information, see our Skinning Tutorial document in the manual
Quantity discounts are available to resellers and developers doing multiple projects, and to OEM customers. Discounts are available on AspDotNetStorefront ML, ML/DNN,
and IS eBusiness versions as follows. Resellers & Developers must be front line support for their clients to qualify for discounts.
|
# Licenses |
%Discount |
|
1 - 2 |
0% |
|
3 - 4 |
20% |
|
5 - 9 |
25% |
|
10 - 14 |
30% |
|
15 - 19 |
35% |
|
20 - 24 |
40% |
|
25 or more |
45% |
Discounts rates can be earned as follows:
a) Earned Discount Rates: Discount incrementally increases as licenses are purchased
in your same account. e.g. when you purchase the first license, it is at 0%
discount. If you then purchase a 2nd license subsequently, it is also at 0%
discount. If you then purchase a 3rd license, it will be at 20%
discount, and so forth according to the discount table shown above, with increasing discounts available as additional licenses are
purchased.
b) Immediate Discount
Rates: Discount can be applied to all licenses purchased at one time.
Discount is computed based on total # of licenses purchased, which results in
the higher discount being applied to all licenses, in trade for buying the
licenses together at one time. If you purchase 16 licenses all at one time, you
will get the 35% discount on all 16 licenses immediately.
This program offers
flexibility for developers & resellers doing multiple storefronts, who want to
trade smaller up front cash flow considerations for graduated discount rates,
versus those who want the maximum discount rate applied to all licenses for
larger initial investment.
For resellers or OEMs doing
special integration projects, please contact
sales for additional
information.
Quantity discounts
rates can not be applied on Standard or PRO versions, or on Custom XmlPackages, QuickBooks T-HUB exporter, or
language packs.
| |
|
|