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.0Questions about migrating from VS 2003 to VS 2005Questions about migrating from VS 2003 to VS 2005
Previous
 
Next
New Post
7/6/2007 3:56 PM
 
We just installed VS 2005 on our PC's and want to upgrade our DNN projects so that we can use ASP.NET 2.0 features like the GridView. We're just not sure if this is such a good idea, i.e. a simple task.

If we simply allow the VS 2005 upgrade wizard do this and then change the .NET Framework version of the virtual directory using a simple tool like ASP.NET Version Switcher (which, by the way, works like a charm), will everything work?

Thank you in advance.
 
New Post
7/9/2007 10:25 AM
 

I didn't find it to be a simple task.  But, then, I was looking for a bit more than just moving it all over.

If I had to do it over again.  I'd use the instructions I just posted here http://www.dmbcllc.com/Articles/WebDevelopment/DotNetNukePAwASPNET20/tabid/260/Default.aspx to create a DNN PA for DNN 4.x and then I'd copy the 3.x files into that project in the correct locations (ie, you'll need to put your business layer in app_code).  If you can get something to convert from codebehind to codebeside for you, great!  Otherwise, you'll need to do that by hand, which isn't difficult, but can be a bit tediuos if you have a lot of ascx/aspx files.

Your other option, which doesn't require the conversion from codebehind to codebeside is to create a web application project.  Personally, I find it frustrating working in WAP because it smells a lot like working in Visual Studio 2003 which I've learned to dislike.

 
New Post
7/9/2007 11:54 AM
 
Christ! That certainly does not sound like an easy task. I will, however, bookmark your very informative article and use it as soon as we decide it's time to migrate. Seems we will have to stick with 1.1 for now.

Thanks a lot for your invaluable feedback!
 
New Post
7/9/2007 4:53 PM
 

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
7/9/2007 5:23 PM
 
The link didn't load.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Questions about migrating from VS 2003 to VS 2005Questions about migrating from VS 2003 to VS 2005


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