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 12:51 PM
 

Oliver, THANKS !

I asume its a bug in the upgrage process....

You saved my last brown hair. How did you found it by the way.

 
New Post
2/26/2009 1:01 PM
 

Jan Olsmar wrote

I asume its a bug in the upgrage process....

You saved my last brown hair. How did you found it by the way.

Jon Henning originally tracked it down I believe, I'd link you to the gemini document but that would cause me to get about a dozen new gray hairs. (Thanks again Jon!)

Then after fixing that bug on all my portals, working with a few users who reported bugs in my Photo Gallery, and just getting done comparing every line of code that was changed between 5.0.0 and 5.0.1 for my svn trunk I use to upgrade all my portals (running 'svn update' is much easier than every other guide on the planet) and realized they missed checking for and fixing this bug on the upgrade (opps).

 
New Post
2/26/2009 1:30 PM
 

Maybe the code should bee like below to minimize the risk for error next upgrade. Anyhow both works.

 

 

 

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

 
New Post
2/26/2009 1:41 PM
 

You are correct, both methods will work. However 5.0.1 will include the xmlns="urn:schemas-microsoft-com:asm.v1" if you upgrade in 5.0.1 to 3.5 framework (i.e.. didn't upgrade your framework in a previous release)... I figured might as well have everyone upgrade to that syntax because it's what 5.0.1 should expect.

 

 
New Post
2/26/2009 1:49 PM
 

Ok, a coin has two sides, If you upgrade a clean 5.0.1 in visual studio the code will look like "mine". Hopefully both will work in 5.0.2 or later.

 
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