Adword Planning

some thoughts:

• keywords and ad text should have good co-relation to improve click-thru
• find keywords with least competition/cost but high conversion chance
• should have a flow to test->analyze->abandon or -> keep[review periodically]
  

Problem Fixed with Telerik Ajaxmanager

I've been stuck the whole afternoon with a problem of ajaxmanager not updating some controls on the page. It turned out that certain control (pagenav) were not visible when not applicable so there was silent javascript error and ajaxman terminated processing on client-side. So remember to check javascript error on similar problems

PaymentSeal Discussion with PSP

PaymentSeal - Notes from discussions

PSP Concerns:

• User (Shopper) Experience - to find out from beta, the experience is similar to sharing an YouTube video on facebook. This is common process in many places (encrypting payment data is new, however)
  
• Idea not Polished/Tested. (nope, that's why I'm proposing to go forward with Beta Testing)

PSP likes:

• Sounds convinced that it has potential. And it's different from current solutions.
• Asked to compare with Paypal. Paypal is an old technique and it has cart abandonment issues. PaymentSeal is similar to many web2.0 login/share procedures and it just might improve cart abandonment.

As a review, I need to keep the points clearer next time. Demo the process and elaborate the details, then reel in with benefits and strategy. Emphasize that the amount of work is minimal. If the beta result is positive, the benefits and the strategy is feasible.

Emphasize that this is not "selling something to PSP", this is executing a strategy together. We have it patent pending and PSP can execute a unique strategy. We all benefit.

The strategy is as follows. PSP license PaymentSeal exclusively (bring to attention that the strategy and benefits work only if this is an exclusive feature.) If PSP balks, offer to sell "Option to License" before beta testing. This will hedge their risk quite a bit.

Running VisualStudio 2003 on Windows 7 (YES. It's Feasible)

As a budget-challenged developer, I have the need to support legacy .net1.1 web applications while upgrading to windows 7. I read some posts about using XP VM, but thought that sounded too complicated. I eventually got it to work using following steps.

Barriers to Overcome:

• Setting up .Net1.1 framework on IIS7 (forgot the details..something like install dotnetfx1.1, install SP1 (very important, IIS7 process will crash unless this is installed/restart) for .net1.1, run aspnetregiis, check the ISAPI filters in IIS manager to make sure 1.1 is available, create new appPool for 1.1)
  
• Install a Vista/Win7 version of FrontPage (not sure if this helped or not, but I installed it)
  http://learn.iis.net/page.aspx/134/installing-the-frontpage-server-extensions-on-iis-70/
• If running Subversion svn, modify to use _svn instead of .svn
  http://blog.dotsmart.net/2008/02/19/moving-on-from-svn_asp_dot_net_hack/
  
• For existing web projects, make sure applications exist in IIS matches that of .webinfo of the projects. i.e.
  
• If opening an existing solution containing web project fails, try removing the web project from the solution, then add it back.