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  |  

AspDotNetStoreFront
  Need Help?  
Professional technical support for DotNetNuke is available from DotNetNuke Corporation.
 


  Ads  
OnyakTech
 


  Sponsors  

Meet Our Sponsors

DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
eUKhost.com is commited to offer exceptional UK Windows Web Hosting solutions with quality 24x7 technical support.Our plans support ASP.Net, ASP, ASP.NET Ajax extensions, XML, MSSQL, MySQL, PHP,DNN, multiple domains and Shared SSL as standard.
SmarterTools
The Official Microsoft ASP.NET Website
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! ( Pr...  Getting Started - VS Express question
Previous Previous
 
Next Next
New Post 4/19/2006 6:03 PM
User is offline robert king
13 posts
10th Ranked


Getting Started - VS Express question 
trying to make a business decision about what tools to use for a fledgling DNN project - I'm equipped with VS2003 EA, so I know I can support and extend DNN 3.2.2

The question is: should I take the plunge and do all the work in 4.0, and can I do everything I need using the VS 2005 Express tools?

Simply put, I can't afford to write M$ a huge check at this point to upgrade my developer tools.
 
New Post 4/20/2006 4:57 AM
User is offline cathal connolly
2656 posts
www.cathal.co.uk
5th Ranked










Re: Getting Started - VS Express question 

It somewhat depends on what version of the .net framework you want to run under.

If you've got vs2003 already, then it's easy just to work with it. Modules created in vs2003 are runtime compatible under asp.net 2.0, so you can upgrade your portal to dnn 4.x (or run dnn 3.2.2 under asp.net 2.0) without an issue, whereas modules created in the express products can't be used under 1.1.

Cathal

 
New Post 4/20/2006 7:42 AM
User is offline robert king
13 posts
10th Ranked


Re: Getting Started - VS Express question 
 cathal wrote

It somewhat depends on what version of the .net framework you want to run under.

If you've got vs2003 already, then it's easy just to work with it. Modules created in vs2003 are runtime compatible under asp.net 2.0, so you can upgrade your portal to dnn 4.x (or run dnn 3.2.2 under asp.net 2.0) without an issue, whereas modules created in the express products can't be used under 1.1.

Cathal



So, there aren't any functional/feature reasons to pick v4 over v3? It all comes down to framework choice?
 
New Post 4/20/2006 12:06 PM
User is offline robert king
13 posts
10th Ranked


Re: Getting Started - VS Express question 
 cathal wrote

It somewhat depends on what version of the .net framework you want to run under.

If you've got vs2003 already, then it's easy just to work with it. Modules created in vs2003 are runtime compatible under asp.net 2.0, so you can upgrade your portal to dnn 4.x (or run dnn 3.2.2 under asp.net 2.0) without an issue, whereas modules created in the express products can't be used under 1.1.

Cathal



So that would involve using the Bin version of DNN 4.0 and only having the modules in any solution/project I work on, right?

Also, I still need some guidance on whether or not VS Express will handle it all.
 
New Post 4/20/2006 12:29 PM
User is offline cathal connolly
2656 posts
www.cathal.co.uk
5th Ranked










Re: Getting Started - VS Express question 

no, there are no functional differences, we keep both codebases syncronised. At some point in the future we will stop developing the asp.net 1.1 codebase, and move exclusively to asp.net 2.0, as it's a large overhead on project resources.

At the minute, the core modules are all asp.net 1.1, and can be compiled/debugged only in vs.net 2003. For asp.net 2.0, we have runtime compatibility, but you cannot compile or debug core modules without some work (rearranging file structures etc.). If you want to develop new modules, targetted to asp.net 2.0, then vb express/c# express are excellent tools for RAD development, particularly as the templates do much of the boilerplate code for you (see http://forums.asp.net/thread/1114393.aspx for more details).

The advantage of the express tools are that they are free, if you feel they're too limiting, or you want to upgrade to vs.net 2005 (or one of the team editions) to access additional functionality, your express projects can be opened in vs.net 2005, so you haven't lost any work.

Cathal

Cathal

 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! ( Pr...  Getting Started - VS Express question
 


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.

 


Softech Development, Inc.
We help your business work smarter with DotNetNuke. Whether you need a new implementation, a custom module or skin for an existing implementation, or integration with your business processes, Softech has the experience and expertise to make it happen.
www.softechdevelopment.com
Module Development by Engage Software
Specializing in custom module development, training and skinning.
www.engagesoftware.com
BataviaSoft DotNetNuke Solutions
BataviaSoft offers custom DotNetNuke solutions especially for the European and the South East Asian market.
www.bataviasoft.com

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