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.0Problems upgrading my module from dnn3.x to dnn4.xProblems upgrading my module from dnn3.x to dnn4.x
Previous
 
Next
New Post
2/1/2007 2:25 PM
 

DotNetNuke 4.x does NOT support the Publish Website menu option in VS2005 or VWD, as it does not support the "Precompiled option" available in .NET 2.  This is because of the way we do Localization.

The best way - in this scenario is to XCopy the files to the remote server - (making sure that web.config is updated with the correct connectionString for the remote site.

I hope this helps.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
2/1/2007 2:34 PM
 

For more information on the various ways to develop modules in 4.x please see the new updated Module Developers Guide.

It is available as part of the Documents package (for 4.4.1) in the downloads section.

Also you can check Michael Washington's Module Development Tutorial site (dotnetnuke.adefwebserver.com)


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
2/2/2007 3:33 AM
 

Yes, I understand the XCOPY issue.  I do not have problems in installing DNN.  My problem is in installing MY module without source.

The problem comes (it seems) when we add a user control into our module.  With source our module works, without source it does not!

I followed Washington's document step by step - in fact that is the one i used.  When I created a simple module (like the one Washington creates as a sample it works) BUT when I add a user control then Washington's step by step does not work!!

 
New Post
2/2/2007 5:32 AM
 
Same thing is happening to me..and i also followed Washington's document...as 'holistic' said the problem is when you add a user control and package the module without source code (using the publish website shown in the tutorial) when the module is packaged with source code it works fine.

Is there a way to package the module without source code without having to do publish website.??

Regards


Ruben
 
New Post
2/2/2007 9:19 AM
 

Michael's tutorial site: "You want to create a DotNetNuke module and you want to distribute it but you don't want to give away your source code?"

This tutorial has information to deploy your module without source: http://dotnetnuke.adefwebserver.com/DotNetNuke/tabid/195/Default.aspx.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problems upgrading my module from dnn3.x to dnn4.xProblems upgrading my module from dnn3.x to dnn4.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