Products

Solutions

Resources

Partners

Community

Blog

About

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.0Using Web Application Projects with DNN 4.xUsing Web Application Projects with DNN 4.x
Previous
 
Next
New Post
5/28/2006 10:23 PM
 

After changing line 18 in EditWidget.asc.designer.vb , the error is fixed.  Thank you.


Fuji Nguyen
FREE Visitor Hit Counter
Visit opensource.indyneinc.com for detail.
 
New Post
5/29/2006 1:18 AM
 
Bertcord wrote

One issue I had was that in the ascx you will see errors for the dnn controls.





I tried this:
<%@ Register TagPrefix="dnn" TagName="Audit" Src="../../controls/ModuleAuditControl.ascx" %>
<%@ Register TagPrefix="dnn" TagName="Label" Src="../../controls/LabelControl.ascx" %>
<%@ Register TagPrefix="dnn" TagName="TextEditor" Src="../../controls/TextEditor.ascx"%>

and the error message went away and does not appear to have any bad side effects.
 
New Post
5/29/2006 7:02 PM
 
yeah! ...the error is gone, however the dnn:label control is still a "not known element".
But still ...using this dev model seems to be a good aproach.
It tried it with my own module and besides the trouble with the DNN WebControls everything seems fine.
I also created a seperated classproject for the SqlDataProvider and got no further compilation errors.
I'm gonne keep on this track trying to get my module running in its own WAP.
...hopefully it's going to work.
keep yu up to date.

good luck
came
 
New Post
5/30/2006 8:25 AM
 
Hi Bert

I added my WAP module project to the WSP core solution, and referenced the project - this built ok. I kept my module code in a separate folder (disadvantage of this is that you have to copy front end pages to the DesktopModule folder after each change - not ideal!) - then I noticed the same problems as you with the user controls, so I took a copy of the controls directory and put it above the module directory (and changed the reference slightly).

This seemd to work ok - still not an ideal dev environment. Now after reading Shaun's post I think his possible solution 1 (release version of WAP DNN core sol) would prob. be best.

Still refining...

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/30/2006 9:12 AM
 
rodneyjoyce wrote
 kept my module code in a separate folder (disadvantage of this is that you have to copy front end pages to the DesktopModule folder after each change - not ideal!)


can you elaborate on this?  Why do you need to copy pages to the desktopmodule folder after each change?  In my solution my files resided in the desktopmodules folder so no copying needs to occur

Bert
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using Web Application Projects with DNN 4.xUsing Web Application Projects with DNN 4.x


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