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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAnyone seen these weird Namespace warnings?Anyone seen these weird Namespace warnings?
Previous
 
Next
New Post
3/30/2014 10:17 PM
 

Warning 16 Namespace or type specified in the Imports 'DotNetNuke' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases. C:\Users\xxxx.xxxx\Documents\My Web Sites\DNN720\DesktopModules\xxxxVB\View.ascx 1 1xxxxVB

 

I'm getting a few hundred of these for a module I'm attempting to migrate from DNN4/5 to DNN7. Since pretty much nothing I'm trying to migrate from DNN4/5 to 7 works I'm assuming this mystery error has something to do with it.

 
New Post
3/31/2014 7:46 AM
 
Those warnings will not stop anything working by themselves.

However - if we assume that you were using things from those namespaces when you first developed the code, it's likely a coded hint that types you *were* using from those namespaces have migrated off elsewhere.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/31/2014 9:41 AM
 
However - if we assume that you were using things from those namespaces when you first developed the code, it's likely a coded hint that types you *were* using from those namespaces have migrated off elsewhere.

That was my assumption, but I'm getting these warnings on ALL DotNetNuke namespaces that are imported into any class file, even references from basically empty .ascx.cs files generated by the template. Since there's no converted code there, it can't be due to an "old" reference. It seems like there's something fundamentally wrong in the project. 

 
New Post
3/31/2014 9:57 AM
 
Your project does have a *valid* reference to DotNetNuke.dll?

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/31/2014 10:41 AM
 

Looking at the references for the project the DotNetNuke.dll looks good, it's referencing the bin folder for the dnndev.me site and the version reflects the version that's there. (latest DNN 7.2.2). 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesAnyone seen these weird Namespace warnings?Anyone seen these weird Namespace warnings?


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out