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.0configuring asp.net  web controls under vs 2005  with dotnetnuke 4.7 ?configuring asp.net web controls under vs 2005 with dotnetnuke 4.7 ?
Previous
 
Next
New Post
11/15/2007 2:43 AM
 

Dear  friend, i want to know how to put  "web asp.net 2.0 user controls (under  visual studio 2005) " into a dotnetnuke 4.7 module.

If  u don't mind, i want a full documentation about this , and the templates used with the visual studio 2005 to create the dnn module.

Thanks for your help .

 
New Post
11/15/2007 8:50 AM
 

All of the documentation along with a VS starter kit is under downloads.  It looks like the latest (documentation) is 4.5.5, but I am sure it will be close.

Also are you just talking regular .Net User Controls?  You can use them the same way you use them with any .Net page.

You might not want to follow the module development that is currently in the doc/starter kit...It has you create the module under the website folder and to deploy it to your live server requires you to "publish" which then creates an assembly per .ascx page (those weird assembly that VS 2005 creates)

You are better off doing it the "old" way.  Create either a "new web site" (file system) or a new "Web Application" (have to have VS 2005 SP1 installed)...This way your modules is it's own project in VS...hence one assembly (unless you split te SQLDataprovider out into it's own).

There is not much documentation on this, but download one of the old modules and you will probably see what I mean.

Hope that helps ya.

 
New Post
11/15/2007 9:07 AM
 

Wolverine wrote

You might not want to follow the module development that is currently in the doc/starter kit...It has you create the module under the website folder and to deploy it to your live server requires you to "publish" which then creates an assembly per .ascx page (those weird assembly that VS 2005 creates)

That describes the process when you need to protect your source code. This describes the normal process:

Super-Simple Module (DAL+) (C# and VB)



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
11/15/2007 10:48 AM
 

Thanks for your help

 
New Post
11/15/2007 5:18 PM
 

Yeah that is the process that I was suggesting to avoid.

We don't do it to "protect" code, we do it for site performance and ease of development.  Also to publish a full site to just get an assembly for one module is a pain as it might take 45 mintues to publish a whole site (depending on the size)

Unless you are just making the .cs files live, which is just a big "no no" for development.  It is fine if you are just using them on your dev serves but when you go live with the code you want to compile them in to assemblies.

We have turned most of DotNetNuke in to assemblies, include the admin and controls folders.  So no source code goes live.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0configuring asp.net  web controls under vs 2005  with dotnetnuke 4.7 ?configuring asp.net web controls under vs 2005 with dotnetnuke 4.7 ?


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