eCommerce Tools and Custom Programming Solutions
v1.0.1.1 of the InfusionSoftDotNet library has been released to support functions and changes related to the Spring 2012 release of InfusionSoft API as well as the latest CookComputing dll (v2.5.0) to handle the XMLRPC communications.
You can download the source code, pre-compiled binaries and or the History.txt file of all changes from http://infusionsoftdotnet.codeplex.com.
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.
From within your storefront’s “Run SQL” option under “Configuration” | “Advanced” (or from within SQL Mangler, I mean Manager, enter the following command:
dbcc checkident(OrderNumbers, reseed, XXXXXX)
Where XXXXXX is the new number you want to use as your seed.
This can come in very handy if you moving from one storefront to another to ensure a continuity of orders.
from: http://manual.aspdotnetstorefront.com/p-1335-changing-the-starting-order-number.aspx
The latest version of InfusionSoftDotNet library to enable Dot Net applications and Asp.Net web applications access the InfusionSoft API was released this morning on CodePlex at http://infusionsoftdotnet.codeplex.com.
One of the biggest changes in this version of the code is the addition of _LastException property to the isdnAPI class to allow you to retrieve any exception thrown during an API call. (Thank cchubb!).
This release is available in full source or as binaries with a sample Asp.Net application. This version will work with Asp.net v2.0 and up.
If you have any thoughts or additions that you’d like to see in this library, please leave a note in the comments below or in the discussion area under this open source project’s CodePlex page.
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
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):
The newly launched AspDotNetStorefront blog launched with a bang recently. In addition to taking advantage of the opportunity to introduce the world to some of their unsung heroes in the Sales and Support department, their first programming tip is something that proved to be quite timely to one of our clients who was experiencing a particular problem with the internal full-text search.
In the past, when doing global search and replaces across text fields in SQL server, I’d been taking the path of least resistance and just writing ASP.NET pages to loop through and performing .Replace() on the SQL column in question.
Of course a devoted programmer, or at least one with more time on their hands, would have instead spent the time trying to find a better way to skin that cat. Well, courtesy of Google, I think I’ve found one. This article from SQLTeam.com all but handed me the answer. Since you can’t use the TSQL REPLACE function against a TEXT (or NTEXT) column the code below will work using UPDATETEXT instead:
Normally, doing a search and replace in SQL is not radically difficult. You basically do an update using the replace() function. For example:
1: Update Product
2: Set Description = replace(Description, 'old text is this', 'new text will be this')
3: where Description like '%old text is this%'
Google announced today that many of the elements of Google apps will no longer support older browers; most notably Microsoft’s Internet Explorer 6.
They are determined to not let lack of support for faster Javascript processing or support HTML5 get in the way of providing a great interface for their customers. As such, after March 1, 2010, Google Docs suite and Google Sites editor will not work with IE earlier than 7.0, Firefox below v3.0, Chrome below 4.0 and Safari below 3.0. Starting next week they will present messages to users to the this effect and recommending that they update.
More importantly, they intend to roll out Google Mail (Gmail) and Google Calendar later in the year. Given that Microsoft has already put out a cry to people to STOP USING IE6, I think that Docs and Sites will not be the death knell but I’m certain that when Gmail stops supporting it, Google will have effectively put the last nail in the coffin of this antiquated web browser.
I say, ABOUT TIME!
What do you think?