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.0How to setup 1.1 modules for dev in 2.0How to setup 1.1 modules for dev in 2.0
Previous
 
Next
New Post
3/19/2008 11:41 AM
 

I have a 3.3.5 dev. env. that happily has seven or eight custom modules.  I would like to move these modules to 4.7 dev. env. in VS 2008.  I have yet to see a posting that details setup of these old modules in the new structure.  Is there such a guide available?

 

Thank You

 
New Post
3/19/2008 11:49 AM
 

We would typically just open them up in VS 2008, convert them to .NET 2.0 Web Applications, and fix any obsolete code references.  While you can use the "new" website model with 2.0 development, now that the Web Application project is standard in VS 2005 SP1 and VS 2008, there's really no need to do much more than just run them through the converter.  Let me know if you have any more specific issues that you run against, I'd lvoe to help.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
3/19/2008 1:33 PM
 

Thanks for the guidance.
I am assuming that in opening them up in VS 2008 you mean:
Copy module from desktopModules directory of 3.3.5 site   to  website\desktopModules directory in 4.7.0 site.  Then while 4.7.0 site project is open, select "Add Existing Project' and browse to VS 2003 project file.  Allow conversion process to take place.  From this point if I build I get an error "Error 1 It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. c:\inetpub\wwwroot\dotnetnuke_2\website\desktopmodules\printrequest\web.config 19"  that points to the web.config the converter created.  Since the project was not to be a stand alone web application I do not go to project listing and convert to web application.  I also do not go to IIS and create application directory.  I could do both of these things but neither will get rid of the error.  I also find that code behind files are not recognized so module controls have ASP.NET runtime error: could not find part of path from the line:  (wrallp being the namespace) 

<%@ Control Language="vb" Codebehind="printRequestView.ascx.vb" Inherits="wrallp.printRequest.printRequestView" Explicit="True" AutoEventWireup="false" TargetSchema="http://schemas.microsoft.com/intellisense/ie3-2nav3-0"%>

 Thanks again.

 
New Post
3/21/2008 11:07 AM
 

While that will definitely work, we usually have each module in a seperate solution, and definitely would have them in a seperate solution from the DNN website (mainly for Visual Studio performance reasons).

Just delete the web.config to get rid of the MachineToApplication error.  VS will add it back sometimes, and you just have to keep deleting it.

When setting up your new project, add a reference to DotNetNuke.dll in your website's bin folder.  Also, on the Web tab, set the Start URL to your DNN site's home page (or wherever you want), set it to use IIS, point to the directory that your module lives in, and then check the Override Application Root, and set that to your DNN site's root URL.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
3/24/2008 9:49 AM
 

Indeed!

Humbled.

Thank You

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to setup 1.1 modules for dev in 2.0How to setup 1.1 modules for dev in 2.0


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