aspdotnetstorefront

Tag: aspdotnetstorefront

Access StoreId from Codebehind in AspDotNetStorefront

If you’ve ever worked in the codebehinds of the latest versions of AspDotNetStorefront, you’ve probably run into this problem before. Or perhaps you’re smarter than me and already knew this in which case, this isn’t for you. 😉

With the new Multi-Store feature in v9.x of AspDotNetStorefront, there are instances where you need to access the StoreId for one reason or another. The problem is, none of the available classes (this, order, page, etc) seemed to be exposing this value. You could look at this.SkinId but this is not an optimum solution since you can add multiple stores to the same Skin.

Read more

SQL Files Grown Out of Control?

For merchants running AspDotNetStorefront who aren’t regularly running the Monthly Maintenance routines, you might find yourself in a situation similar to one of our clients where the size of the transaction log for their SQL database had grown large enough that their site was shut down because it couldn’t grow any more.

In this case, since we couldn’t access the admin section of the site to run the monthly maintenance, I was able to run the following commands in order to clear the transaction log to the point of the last backup AND then shrink the physical size of the SQL database files. Please note that before running these commands GET A FULL BACKUP OF THE DATABASE. If you can’t do this directly from SQL Management Studio (or similar tool) you should be able to initiate an ad-hoc backup from your hosting company’s control panel.

Read more

Quickly Map Manufacturers to Store in ASPDNSF Multi-Store solution

image I’m sure you’ve been there before. You (or your customer) have gone in and added all your products and defined which products go with which stores but then decided after the fact that you want to have a manufacturer’s page (or menu) that shows all the manufacturers of products that  exist in a give store on your Multi-Store solution.

Read more

Running Asp.Net 4.0 Application on IIS6 under Asp.Net 2.0 Parent App

Phew, that title sure is a mouthful… but it is kinda hard to describe the problem in so few words.

I had just finished the primary work on a new customer’s website (http://www.BuyMyBatteries.com) and was trying to hook up the latest and greatest build of BlogEngine.Net (2.5) underneath it for the corporate blog.

The challenge, as you might have guessed is that while BE.NET requires Asp.Net 4.0, the server was running IIS 6.0 and more importantly, the parent website is running ASP.NET v2.0. Resolving this took a number steps but it appears to be working quite nicely now

Step 1

Read more

How To Extend ASPDNSF Product Name Field

On of the nice features of AspDotNetStorefront is that it supports multiple languages right out of the box. It does this by storing the multiple locale phrases as XML fragments inside the particular field. So, in the case of a product name, this means stuffing each of the multi-lingual product names into the Name field in the Product table. It also needs to be properly defined in this field with the XML code so a sample, multiple language name field could contain something similar to the following:

<ml>
    <locale name=”de-DE”>CMS-6R4</locale>
    <locale name=”en-US”>CMS-6R4</locale>
    <locale name=”fr-FR”>CMS-6R4</locale>
    <locale name=”ja-JP”>CMS-6R4</locale>
</ml>

Read more

AspDotNetStorefront Acquired by Vortx

image Wow, just when you think certainly areas of your life are pretty stable… Vortx, a leading integrator of AspDotNetStorefront software in Ashland, OR,  announced yesterday that they had acquired the Ohio-based ecommerce company.

One interesting tidbit that can be found on the press release is that they are planning a marketplace of plug-ins. Hopefully this will be more along the lines of the Android app and Google Apps marketplaces than the iPhone app marketplace, if you get my drift.

Not surprisingly, AspDotnetStorefront website has no press release up about this acquisition.

More details to follow as it is released.

Incorrect Namespace Error in Google Webmaster Tools

If you are using AspDotNetStorefront, as well as possibly many other web applications, you may have noticed lately a number of errors showing up in your Google Webmaster Tools account. The error status indicates “Your Sitemap or Sitemap index file doesn’t properly declare the namespace.” or simply “Incorrect namespace” in the urlset tag.

Incorrect namespace in the urlset tag.

Read more

Deciding Which AspDotNetStorefront Is Right For You

A while ago, I wrote about how to decide which of the various versions of AspDotNetStorefront were right for your application. I think the guidelines in that article still hold true but now that there are more versions of the software available, it should be updated. Thankfully, the fine folks at AspDotNetStorefront have already done so in their blog. Here are some of the updated deciders (my comments on each of their points are added in blue italics):

Read more