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.0Module development with the “WAP” method.Module development with the “WAP” method.
Previous
 
Next
New Post
6/25/2008 10:24 PM
 

I have a question for my fellow DNN developers who are using the WAP method of module development. For the last two years I have been using the WSP method of module development. And it worked alright but to speed up packing of modules I switched to the WAP method. I’ve gotten everything to work but I have a “thorn in my side” problem. It seems that no matter what I do, I get this following error message when I try and use the dnn controls.

 

This line of code:

<%@ Register TagPrefix="dnn" TagName="Label" Src="~/controls/LabelControl.ascx" %>

will cause this error:

Error 1 File '~/controls/LabelControl.ascx' was not found.  C:\CompiledModules\Old\MyModule\MyModule\MyModule\Settings.ascx 2 51 MyModule

 

In the WSP method this would work fine and there would be no errors, and Intellisense would work. Despite the error, this module will compile and it will run fine. But on some of my larger forms, I get 1500+ page errors from missing dnn controls. It’s making it difficult to find the real errors, and without Intellisense it’s getting hard to catch typos. I understand why it’s causing an error; the label control is no longer in this project. Is there a way to reference the control so that this error goes away and my Intellisense comes back?

 

Thanks,

 

Nathan Rover

 
New Post
6/26/2008 9:35 AM
 

Hey Nathan,

What version of Visual Studio are you using? I generally see these Label control messages show up only when I've actively got the module control in question open (otherwise I don't see them at all).  Also, it certainly has never had any effect on my intellisense. Really what I mean to say is - this hasn't been as big of a deal for me when using VS 2005 or VS 2008 - so I suspect you may be using VS 2003?

Thanks,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
6/26/2008 11:39 AM
 

I’m using VS 2005. And you’re correct; the error goes away when the .ascx page is closed. My problem with it is that if there is a real error on the page and I have a few hundred of these errors it makes it difficult to find the real error. I might not have been clear about the intellisense, it works for everything but these controls so if I go to type <dnn:label ID=” etc… the intellisense doesn’t kick in like it would with non DNN controls.

 

Thanks,

 

Nathan Rover

 
New Post
6/27/2008 10:58 PM
Accepted Answer 

Well, I’ve figured it out. It seems all I have to do is copy the controls folder from a stock DNN install to my module project and make sure I have a reference to the dotnetnuke.dll file. Then I exclude the files from building in my MS build scripts, I’m not sure if that last step was necessary. It seems easy now… can’t beat that feeling of no red “X’s” and no yellow “!”. Hopefully someone else will find this as helpful as I did.

 

Thanks,

 

Nathan Rover

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module development with the “WAP” method.Module development with the “WAP” method.


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