Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Changes to how VB.NET handles scope in VS2005Changes to how VB.NET handles scope in VS2005
Previous
 
Next
New Post
5/1/2006 7:35 AM
 

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]


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/10/2006 4:18 PM
 

Having the same problem - need to go through and add all the required imports.

Version Info:

Microsoft Visual Studio 2005
Version 8.0.50727.42  (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005   77626-009-0000007-41183

-- Update
realized I had a 'duh' moment.  Needed the .config file to be web.config and NOT app.config.  all worked fine then.

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Changes to how VB.NET handles scope in VS2005Changes to how VB.NET handles scope in VS2005


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out