Triggered by this post: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/21497/scope/posts/Default.aspx and my own experiences with compiling the DNN 4.03 starterkit on a freshly installed pc running the latest version of VS2005, i found out that there must have been some change in how the VB.NET compiler handles scope between the November 2005 release of VS2005 and the December 2005 release. If you look in the about box of VS2005, you will see version numbers of all installed languages, the versions of the November 2005 release end with 41040 (eg. 77642-113-3000004-41040 for vb.net), while the versions of the vs2005 release ends with 41696 (eg. 77642-113.3000004-41696)

The only way i could get the starterkit to compile is to add imports to all appropriate namespaces to all files that gave problems (95 or so files ;( )

Maybe i'm just being extremely crosseyed, but i think this is a serious problem. Maybe people working with vs2005 and dnn could report their version of vb.net here, and also whether they experience problems or not?

Cheers,

Erik

[edit]PS: see more about this problem in this thread: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/21497/scope/posts/Default.aspx [/edit]