Download DOWNLOAD
Forums FORUMS
Blogs BLOGS
Forge FORGE
Help HELP
Marketplace MARKETPLACE
DotNetNuke Home
You are here >   Community > Forums
Register  |  Login

DotNetNuke Forums

DotNetNuke ForumDotNetNuke ForumArchived 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/27/2006 3:09 PM
 

I was able to put together a sample that uses both the Web Site Project type and the Web application Project type.  As Shaun mentioned in this blog post http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/434/Default.aspx  the core needs to always be available as a Web Site Project to support users that are using the Express edition of Visual Studio.

To use this sample you will need to download WAP here. http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx

The approach I took was to create a web application project within the directory of the website project.  To create the sample I took the following steps

  1. Create new DotNetNuke website using starter kit
  2. Add express database and make sure site works
  3. Add widget module using directions from this link http://forums.asp.net/thread/1114393.aspx
  4. Remove Widget files from app_code and desktop modules.  I did this so I could create the WAP for the widget module
  5. Add WAP for the widget module in the desktop modules folder of WSP I had created in step 1, copy the files back into this directory.
  6. Add code directory to widget folder and add files that I took from the APP_code directory
  7. In visual studio select show all files and include the files in the project
  8. right click each control and convert
  9. On the project properties set the build directory to the BIN of the main solution
  10. I had to add a few DLL references and add some import statements

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


This could be resolved if these controls were converted to server controls.   I was also able to debug by attaching to the aspnet process.

You can download my sample solution here

http://www.corderman.com/DNN1.zip

Bert

 

 

 

New Post
5/27/2006 10:44 PM
 
Q: Would a conversion of DNN controls from user controls to server controls represent a breaking change?
New Post
5/28/2006 7:14 AM
 

Donwloaded, followed instructions.  Two errors related to the code below

txtContent.Text = objWidget.Content

objWidget.Content = txtContent.Text

The error is 

'Text' is not a member of 'System.Web.UI.UserControl'. C:\Documents and Settings\fnguyen\Desktop\wap\DNN1\WebSite\DesktopModules\Widget\EditWidget.ascx.vb 127 37 Widget

After commented out these two lines, compiled success.  Verified that widget.dll is in the dotnetnuke bin folder.

Coping "controls" folder from dotnetnuke mainfolder inside the desktopmodule\widget does not seem to resolve the error.


Fuji Nguyen
FREE Visitor Hit Counter
Visit opensource.indyneinc.com for detail.
New Post
5/28/2006 7:32 AM
 

Obviously the old usercontrol based controls would need to stay for backwards compatibility.  So no this would not be a breaking change. 

New Post
5/28/2006 1:23 PM
 
hum...dont know how I missed that one...anyhow here is the fix

Line 18 of EditWidget.ascx.designer.vb is wrong
change
Protected WithEvents txtContent As System.Web.UI.UserControl
TO
Protected WithEvents txtContent As DotNetNuke.UI.UserControls.TextEditor

I updated the zip
Previous
 
Next
DotNetNuke ForumDotNetNuke ForumArchived 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

Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Networks

Follow DNNCorp on Twitter Follow DNN Community on Twitter

LinkedIn

Sponsors

DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation

Hosted by MaximumASP