One of the frustrating things currently about DNN and some of its core modules - is that those modules are currently NOT always source compatible with ASP.NET 2.0

In some cases the source code will be for ASP.NET 1.1 and the project targeted at VS2003.

>>>>

Unfortunately - this is not made clear currently on the DNN site for all mdoules

There are some clues to this if you look in the code - that will let in know what you are dealing with.

If you download the SOURCE code for the BLOG - you will find firstly that the currently available version for download has a last modified date on most of the files on 22/12/2005.  -  so the source code is a little old - the older it is the less likely to be 2.0

If you dig further - and look at pretty much any ascx.vb file in the install - you will see that the way the module classes are defined is incorrect for asp.net 2.0 and dnn4.x - they are defined as Must Inherit instead of Partial.

In addition, if you open the vbproj file in a text editor - and look for the framework statement - it should show the version of asp.net the project is currently targeted too.

>>>>>>>>>>>

Ok - so what can you do about this ... one place to start is the Module Wizzard in the DNN downloads area - which can assist in the conversion of a module from asp.net 1.1 to asp.net 2.0 compatibility.

Note however - that to do this you will most likely need to setup a DNN 3.x portal running asp.net 1.1 to get things happening.

>>  The wizzard does a reasonable job of handling the most common issues - and as best as I can seems to have been used to port forward at least some of the core modules.

Your other option is to start hacking away at the project yourself - file by file - do a search of the blogs here on the site - I seem to recall there being at least one blog that discusses how the wizzard works - and essentially what changes are being made.

Westa