Custom Module Error - Using Modules and Other Extensions

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

Home All Forums

1
2
3
4
5

11/14/2011 8:08 AM

mona 2010

Joined: 5/4/2011

Posts: 53

Custom Module Error

hii all,

I face aproblem after installing DotNetNuke Compiled Module and Adding New Project .
When i Build The Soultion , alot of errors appear telling

"The type or namespace name 'Provider Configuration' could not be found (are you missing a using directive or an assembly reference?) in DotNetNuke Compiled Module" and

"The type or namespace name 'Common' could not be found (are you missing a using directive or an assembly reference?) in DotNetNuke Compiled Module" and

alot og these arrors

So, Any One Can Help Me ,Please....

Thanks

11/14/2011 12:59 PM

Ian Robinson

enlivenhq.com
Joined: 1/6/2006

Posts: 921

Re: Custom Module Error

mona2010 wrote:
hii all,

I face aproblem after installing DotNetNuke Compiled Module and Adding New Project .
When i Build The Soultion , alot of errors appear telling

"The type or namespace name 'Provider Configuration' could not be found (are you missing a using directive or an assembly reference?) in DotNetNuke Compiled Module" and

"The type or namespace name 'Common' could not be found (are you missing a using directive or an assembly reference?) in DotNetNuke Compiled Module" and

alot og these arrors

So, Any One Can Help Me ,Please....

Thanks

Hello,

Have you checked the assembly reference for DotNetNuke.dll? Expand the References section of your project and If it is displaying a warning symbol next to DotNetNuke, try deleting it and then adding it back. You can reference the DotNetNuke.dll that is located in the website's "bin" directory.

I believe the template you are using assumes a specific relative path to the assembly - so if you have created an extra level (like using a parent module folder inside of desktopmodules) that relative path may be wrong and this could cause the symptom you are seeing.

Hope that helps,

Ian

Software Engineer

Leader, St. Louis DotNetNuke User Group

Co-Founder, dnnGallery

Stack Overflow: Ian Robinson

Twitter: @irobinson

Linked In: Ian Robinson

Page 1 of 1

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)