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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...5.0.0 to 5.0.1 upgrade5.0.0 to 5.0.1 upgrade
Previous
 
Next
New Post
2/26/2009 11:52 AM
 

Haven't gotten to the upgrade yet, still working on merging the 2 branches...

Anyways, I did notice the App_Browser folder did not get renamed to App_Browsers

I'm using the Source zip... Haven't bothered to check the others yet...

 
New Post
2/26/2009 11:56 AM
 

THANK YOU!   This worked for my install.

 

 
New Post
2/26/2009 12:24 PM
 

As for the other issue with the System.Web.Extensions... 

I haven't verified this in anyway, but I believe the problem has to do with a bug that was in the "Upgrade Framework" web.config merge.

Can you check your web.config before you delete that dll?

The bold bits needs to get deleted, that should get your site going again. I think...

      <dependentAssembly xmlns="">
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly xmlns="">
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>

Also, making sure the xmlns="" bits are removed will allow your portal to run modules compiled for both asp.net 2.x and 3.5 without erroring out due to the version mismatch on the system.web.extensions dll

 
New Post
2/26/2009 12:34 PM
 

I also have experienced issues with system.web.extensions.dll file. I assume this file is being inherited from GAC in Medium Trust environments and causes errors during upgrade.

My previous attempt was upgrading from 4.9 to 5.0 but it failed with generic error like you posted.


Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey
 
New Post
2/26/2009 12:36 PM
 

Ok, I have verified this now, and the web.config is the root cause.

If you clicked the "Upgrade to Current Framework" button in Host Settings on DNN 5.0.0 (or any of the previous RC's), then you probably have bug...

You need to manually edit your web.config, it should be around line number 243ish. I was slightly wrong above (although it will still work), the DNN 5.0.1 method is to add the "urn:schemas-microsoft-com:asm.v1" into the empty xmlns=""

Below you'll find a fully working section.


 <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="bin;bin\HttpModules;bin\Providers;bin\Modules;bin\Support;" />
      <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...5.0.0 to 5.0.1 upgrade5.0.0 to 5.0.1 upgrade


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