Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

PortalWebHosting
  Ads  
OnyakTech
 


  Sponsors  

Meet Our Sponsors

Portal Webhosting - Hosting For Developers
Red-Gate Software
MaximumASP
SourceGear - Tools for Developers
.: CounterSoft :.
telerik
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! (Pro...  Development Strategy
Previous Previous
 
Next Next
New Post 7/20/2008 12:38 PM
User is offline Duncan Ion
12 posts
10th Ranked


Development Strategy 

Hi,

I'm just moving from my VS2005 environment to VS2008.

Can anyone advise on the following?

1. Is it OK to move to the .net 3.5 framework?
    I'm developing on a Vista Ultimate with IIS 7.0, so how do I switch to 3.5? [Currently set to the Classic .net AppPool]
    I also read that switching to Pipeline integaration was an advantage - Is this correct?

2. Mitch Sellars mentioned that the WAP development approach was good. I currently use the 'vlado' approach - that is, I have my module files in the DesktopModules folder of the DNN website and add the project file to the solution. This has working well - is the WAP approach better?  How do I do that?

3. If I can switch to 3.5 framework, I assume that I can also move to the 3.5 version of AJAX. Any problems with that?

If there was a single point of guidance for these questions, That would be terrific.... is there one?

 

thanks in advance

regards,
Duncan.

 

 

 

Given that

 
New Post 7/21/2008 10:18 AM
User is offline Mitch Sellers
5719 posts
www.mitchelsellers.com
3rd Ranked




Re: Development Strategy 

Duncan,

There are no problems in upgrading to using .NET 3.5.  You will want to be sure to be on 4.8.0 or later as it has the fixes needed to run in pipeline mode.  You can simply change your virtual directory settings away from the Classic .NET App Pool to make the first step of the change.

WAP is done using a separate template, I find it easier as you get the ability to have post build events, solution files, and easily created .dll files for the modules, but not everyone likes working that way.


-Mitchel Sellers
MCITP, MCPD, MCTS
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Consulting Quotes, and DNN Technical Support Services

I reccomend 3Essentials for shared hosting and BaseCamp for project management
 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! (Pro...  Development Strategy
 


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.

 


TechNexxus
Business process and technology sourcing solutions delivering superior people, process and value. We have used, and continue to use, DNN successfully in numerous client projects to deliver exceptional value. We are proud to support the DNN team and community.
www.technexxus.com
PartnerPoint | Community of Microsoft Partners
PartnerPoint is one of the largest and most active online communities of Microsoft Partners worlwide with over 8,000 members.
www.PartnerPoint.com
Web Valley
Website design, Database development
www.webvalley.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP