<p>My <a href=http://www.restaurantthing.com>Restaurant Thing</a> is a busy site - it has thousands of users and can see 10k hits on a busy day.</p> <p>I'm looking to migrate it from my own ASP.NET architecture to being a <a href=http://www.dotnetnuke.com>DotNetNuke</a> site. </p> <p>This really shouldn't be too difficult - I implemented the 'back end' stuff as a web service, so I can continue to use the web service for the new site (actually leaving them both running for a while). I need to create DotNetNuke modules for all the functionality that the site offers, which at this point I think is just a 'List' module, a 'Detail' module, a 'Search' module, and some way for these modules to talk to each other.</p> <p>The first step was writing a skeleton module, which I just finished: I have a DotNetNuke module that connects to the web service and simply shows the number of restaurants in the database. Cool.</p> <p>I put my first new module on the <a href=http://www.stevex.org>front page of my site</a>.</p>Thu, 01 Sep 2005 19:17:08 GMT