Sorry about that. It should be there now.

Actually the process is quite straight forward once you update the Starter Kit template. I will be merging content from my blog and this site into a single resurce repositor and will probably update some articles. What is it that you find complicated?

I used the available Starter Kit VB template but one for C# can be used as well reproducing the steps. No C# actual code is touched and the mentioned .vb files can be replaced by their C# counterparts.

The article doesn't mention anything about the Dotnetnuke upgrade process itself as it is covered in several other places, including the Dotnetnuke documentation available from the downloads section. In a nutshell test the upgrade for DNN first to see if your modules break.

Once you have your development environment set up, refer to the article to move your DNN 3 modules to work in DNN4 as wap modules (compiled dlls).  From my experience, it's just a matter of correcting the compilation errors that might show up. I have found very few errors that prevent compilation after moving a module from DNN 3 to DNN4. The real work comes if you want to update your code to use the asp.net 2.0 framework, but it's not always necessary as it is backward compatible.