I'm gob-smacked that the DNN Store module has such fundamental bugs as sending customers order confirmation emails that show their address as just being Afghanistan. How can anyone ship that as a finished product?

So I decide to do something about it rather than sitting on my arse and moaning, or shelling out good money for a 'commercial store' chosen from what appears to be a pretty poor selection.

Download DNN 4.9.0 src and spend 3 train journeys (30 mins each) to get that working:

• Problem: no web.config file
  
  A: copy development.config to web.config
  
  
• Problem: isn't using VS2008 internal webserver like it used to - don't know if this is something I've changed in VS or not.
  
  A: establish it's using IIS - get that started
  
  
• Problem: decide that I want a separate source area for working on the store rather than the core dnn code. Copy dnn src directory to another one. all sorts of wierd problems come up
  
  A: new directory was hooking into old directories IIS alias ?!? edit the new directories .sln file to change localhost\DotNetNuke_2 to localhost\DotNetNuke_3 and next time I fired up VS it creates the necessary in IIS
  
  
• Problem: infinite redirection
  
  A-not: edit the PortalAlias table via VS to create a new alias
  
  
• Problem: DotNetNuke can't access the database anymore
  
  A: close the database connection in VS after every time I make a change (seriously annoying!)
  
  
• Problem: Still got infinite redirection
  
  A: spend ages and ages searching forums and blog to finally discover that all I needed to do was replace every instance of Version=1.0.61025.0 with Version=3.5.0.0 in the web.config file (obvious really). Thanks time 10million to this webpage that gives the various solutions for different causes: http://bestwebsites.co.nz/dotnetnuke/solving-the-dotnetnuke-redirect-loop/
  
  
• Problem: Can't figure out where the store module code is, as it doesn't appear to be in the source download
  
  A: turns out it's in the .resource file inside the zip - the way to get to the source is to install the source version of the module from within dnn itself and that puts all the right source in the right places. This forum post gives a really good description of the process: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/114/threadid/186305/scope/posts/Default.aspx
  
  
• Problem: FileIOPermission exception whenever I try to add a page, view the host settings, or most other interesting things
  
  A: ok - some .net runtime version mismatch. Getting fed up now - can't be messing with this stuff, I've got code to write. Took a punt and changed all of the Version=3.5.0.0 's back to Version=1.0.61025.0 's and changed the trust in the web.config from Medium to Full, and reapplied the ASPNET 'full control' NTFS permission to the whole web-tree