Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Trying To Update from ealier version (both .NET and dotnetnuke)Trying To Update from ealier version (both .NET and dotnetnuke)
Previous
 
Next
New Post
5/12/2009 11:32 AM
 
jeff finn

Joined: 5/11/2009
Posts: 3

Before I go into much detail, I would like to warn anyone who reads this that it is going to be rather horrifying.  You have been warned.
Also, if this is the wrong forum topic I appologize.

 

I have been tasked with bringing our web projects 'up to date'.  Our current dotnetnuke version is 3.3.7.26027 compiled from VS2003 on .net1.1
We want to bring it to .net3.5 in VS 2008 on the latest build of dotnetnuke.  I've been attempting to do this for some time, with limited success.  I've followed the upgrade guide, as far as file copying and web.config file changes go, however, thats the least of my worries really.  After project conversion, I am getting 118 errors, a few examples include:

Error    1    Unable to convert to Web Application format because the code-behind file 'admin\Skins\skin.vb' does not exist.    C:\Carrier Load\Code\Portals\_default\Skins\DNN-Gray\Vertical Menu - Full Width.ascx    1   
Error    9    Unable to convert to Web Application format because the code-behind file 'admin\Containers\container.vb' does not exist.    C:\Carrier Load\Code\Portals\_default\Containers\DNN-Gray\Text Header - Color Background.ascx    1   
Error    32    Type 'DotNetNuke.UI.WebControls.DNNLabelEdit' is not defined.    C:\Carrier Load\Code\admin\Containers\Title.ascx.designer.vb    26    42    DotNetNuke
Error    33    Type 'DotNetNuke.UI.WebControls.DNNToolBar' is not defined.    C:\Carrier Load\Code\admin\Containers\Title.ascx.designer.vb    35    44    DotNetNuke
Error    34    Type 'DotNetNuke.UI.WebControls.DNNToolBarButton' is not defined.    C:\Carrier Load\Code\admin\Containers\Title.ascx.designer.vb    44    41    DotNetNuke

I know these errors are mainly caused from the VS2008 conversion tool and not dotnetnuke itself, and obviously there are many many more.
I was hoping someone had been through this and there is a step I have missed.  My gut feeling is I will have to start with a new project and re-write the code, but I would like to avoid this if at all possible for obvious reasons.
 
New Post
5/12/2009 2:52 PM
 
Mitchel Sellers


Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

www.mitchelsellers.com
Joined: 1/24/2007
Posts: 7846

Are you doing WSP module development with the existng site?  I'm guessing so, since you are working with a project.

I would almost recommend upgrading the site first (3.3.7 -> 4.4.1 -> 4.6.2 -> 4.9.3), then open the new solution and add the projects to the solution....

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
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 Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/12/2009 3:13 PM
 
jeff finn

Joined: 5/11/2009
Posts: 3

Honestly, I don't know about the WSP thing, I didn't even know dotnetnuke existed until late last week, so lets assume your assumptions are correct....
However, I am fairly certain I am working with just the site, as you put it.


I have not tried the incremental upgrade, if you think that will help, I will go for that.
 
New Post
5/15/2009 10:09 AM
 
jeff finn

Joined: 5/11/2009
Posts: 3

Alright, I decided working with the source project was just too much.

I got a fresh install of dotnetnuke, I brought the module code to 2.0 code recompiled and made the one version change needed (DataCache.ClearTabCache to DataCache.ClearTabsCache).  put the dlls into the bin folder, copied my Code folder into DesktopModules.  Made the sql connection and machine key adjustments to the web.config, then brought up the page and let it do its Upgrade.

I got one error
00:00:04.468 -   Executing Script: 04.04.00.SqlDataProvider Error! (see 04.04.00.log for more information)

I wasn't ever able to find that log file, so no idea what happened there.
Then when I tried to map to my Default.aspx page, I got a Redirect Loop.

I tried every single fix I could find on this.  My Alias was fine, I tried removing the Web.Extension.dll from bin and upgrading the assembly reference to 3.5.0.0, and even tried the old version of the Default.aspx page, nothing worked.

I get to the same dead end when I try an upgrade with the already existing Folder (instead of using a fresh install) and copying over the existing folder with the new install files.


Is there any way to fix this?
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Trying To Update from ealier version (both .NET and dotnetnuke)Trying To Update from ealier version (both .NET and dotnetnuke)


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