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.0Develop with DNN 3.2.2 or 4.0.2?Develop with DNN 3.2.2 or 4.0.2?
Previous
 
Next
New Post
4/13/2006 1:05 PM
 
Hi Folks,

I'm trying to get my head around which DNN version would be better for creating .NET 2.0 modules.  I'll be using VS 2005.  I want to target both DNN 3.2.2 and 4.x.

Questions
- Will modules built using the 4.x starter kit and VS 2005 with precompilation, like Shawn's final example, run in DNN 3.2.2?
- Do folks prefer using the VS 2005 Web Application Project add on (http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx), or the multiple precompiled DLLs Shawn describes?
- Pros and Cons?

Any other advice?

Thanks,
Wylie



Chris Wylie
Chief Executive Officer
www.AccordLMS.com
1775 W. State Street Suite 371, Boise ID 83702 USA
 
 
New Post
4/13/2006 6:10 PM
 
if you want to target 3.3.2 then you cannot use VS2005
 
New Post
4/14/2006 12:48 PM
 
Thank you for your reply Bertcord.

Is this true even if I'm running 3.2.2 on top of .NET 2.0?  Is this a limitation of DNN 3.2.2?

Thanks,
Chris



Chris Wylie
Chief Executive Officer
www.AccordLMS.com
1775 W. State Street Suite 371, Boise ID 83702 USA
 
 
New Post
4/18/2006 1:31 PM
 
The projects and compilation model (IIRC) for 3.x is designed for VS2003.  VS2005 is not backwards compatible.  :-/
 
New Post
5/1/2006 11:13 AM
 

jbeall wrote
The projects and compilation model (IIRC) for 3.x is designed for VS2003.  VS2005 is not backwards compatible.  :-/

While a DNN4 website cannot be "swapped over" as a DNN3 website, making a module in DNN4 should port over to DNN3. (The differences in the projects & compilation module for VS2003 / VS2005 is significant for the site as a whole, but can be "worked around" for basic module development.)

To develop modules in VS2005 for both DNN3 & DNN4 platforms, you need to

  • Add your module's folder name to the following part of the web.config file

    <!-- register your app_code subfolders to generate granular assemblies during compilation

    <codeSubDirectories>

    <add directoryName="ModuleFolderName"/>

    </codeSubDirectories>

    -->
    The <codeSubDirectories> tag will, of course, have to be un-commented to be workable. Basically, what this will do is give you a bit more control on the creation of the .dll for your module (so that you can package it easily).

  • You will need to right-click your website "project" and choose "Publish Web Site" to generate the .dll files to include in your module's installtion zip.

That's the basics of making them cross-portable. I may have missed some small details (doing this off the top of my head), so if anyone can add info, that would be great!

- Dan

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Develop with DNN 3.2.2 or 4.0.2?Develop with DNN 3.2.2 or 4.0.2?


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