OK, for anyone interested, here's how far I've got (pretty much starting from scratch after my last post):

-Install DNN 3 from Source
-Install DNN 4 using starter kit File->New Website (equivalent to doing it from source?) in a separate location
-Extract the Store module source (from the .resources file) to [DNN3]\DesktopModules\Store
-Run the module conversion wizard taking the store from the v3 site to the v4 site
-Open the v4 site again in VS2005

Got lots of errors in globals.asax, fixed some by:
adding "Imports System.Web" to the imports section; apparently this step is missed out by the module converter.

I'm still getting problems because the following imports aren't working, leading to multiple "Name '....' not defined/declared" errors:
-DotNetNuke.Security.Roles
-DotNetNuke.Services.Log.EventLog
-DotNetNuke.Upgrade
Presumably these are in their own DLL files but I don't know where to find them (they're not in [dnn4]\bin).

Any more help?

Actually, I got impatient and downloaded C# express 2005 instead of waiting for my new copy of VS2005 to arrive

So I attempted to convert the project - it took about 30 mins and was sucessful

Here is how to convert a 2003 DNN project to 2005 DNN project (should work for any 2003 DNN project, VB or C#)

1. Install the .install version to your DNN website
2. Copy the .source version to somewhere else (anywhere not under the web root directory)

3. Open the project in C#2005 express (or VS2005)
4. Project upgrade wizard launches, click Next until it finishes
5. Upgrade should complete with no errors and several warnings

6. For each project in the solution (20 of them in the store solution), check the references
6a. If it refers to DotNetNuke, remove reference and add new reference to the DotNetNuke.dll located in your website/bin folder
6b. Repeat for CountryListBox (new location is website/bin)
6c. Repeat for Microsoft.ApplicationBlocks.Data (new location is website/bin)
7. Remove the project DotNetNuke from your solution (we only refer to it by file reference to the .dll now)

8. Build solution - you may get compile errors
9. Add a reference to DotNetNuke.dll for any projects that have compile errors.  In the store solution this means the DotNetNuke.Store.WebControls project
10. Rebuild solution - Success! :)

11. Optional - the projects all build .dlls to their own bin directory eg DotNetNuke.Store.WebControls/bin/release.  Change the projects so that they all build to the sourceroot directory/bin/release.

12. Note that if you move the website directory then your references will break.  Go back and reset them to the new location after moving.

13. Make any changes you want to the project
14. Compile
15. Copy your new dlls to website/bin

Easy as that :)

JK

---