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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Reference required to assembly Telerik.Web.UIReference required to assembly Telerik.Web.UI
Previous
 
Next
New Post
12/14/2010 4:36 PM
 
I am still having issues with a 5.5.1 upgrade to 5.6 here is my error:

DotNetNuke Error


 

Error An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: D:\www-root\DNN_01_Test\Default.aspx(32): error BC32206: The project currently contains references to more than one version of Telerik.Web.UI, a direct reference to version 2010.2.713.35 and an indirect reference (through 'DotNetNuke.Web.UI.WebControls.DnnWindowManager') to version 2010.2.929.35. Change the direct reference to use version 2010.2.929.35 (or higher) of Telerik.Web.UI. ---> System.Web.HttpCompileException: D:\www-root\DNN_01_Test\Default.aspx(32): error BC32206: The project currently contains references to more than one version of Telerik.Web.UI, a direct reference to version 2010.2.713.35 and an indirect reference (through 'DotNetNuke.Web.UI.WebControls.DnnWindowManager') to version 2010.2.929.35. Change the direct reference to use version 2010.2.929.35 (or higher) of Telerik.Web.UI. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String virtualPath, String path) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---


Here is the dependentAssembly part of my webconfig...

<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <!--Upgraded by .NET 4.0 Upgrade version 5.4.4 - Date: 7/22/2010 8:50:53 AM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <!--Upgraded by .NET 4.0 Upgrade version 5.4.4 - Date: 7/22/2010 8:50:53 AM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.4.0 - Date: 5/25/2010 4:46:17 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.4.0 - Date: 6/28/2010 4:07:32 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 8/25/2010 8:49:36 AM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 9/23/2010 11:08:49 AM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" />
      </dependentAssembly>

Any Thoughts?
 
New Post
12/17/2010 10:27 AM
 
Anyone? I have upgraded 5 sites to 5.6 no issues... this one is giving me greif there is nothing different between this instance and the rest. Different sites yes... but same modules and settings.

Any other thorughts?
 
New Post
12/27/2010 5:49 AM
 
I am facing the same issue (Multiple references of telerik DLL) while upgrading the DNN version from 04.09.00 to 05.06.00.
Before update, I am using telerik version 2008.3.1125.35. After updation it automatically updated to version 2010.2.929.35(This is the default verison of telrik DLL provided in the DNN version 5.6).

I have checked in web.config file, as you mentioned in above reply:

1. (Before updates, these lines are not available in the web.config, below lines has been added after updation)



2. Check the version of telerik DLL in the bin directory, found that it has also been updated from
2008.3.1125.35 to 2010.2.929.35.
Run the application with the above settings (Web protal has been run successfully, but this time it is using telerik version 2010.02.0929.353 and we are facing lot of designing issues with the new version of telerik DLL)
Our basic requirement is to upgrade only the DNN version bot not Telerik DLL verison.

3. Removed the reference of telerik DLL 2010 verion and again added reference of old 2008 telerik DLL version.
4. Changed the settings in web.config file.(Chnaged the newVersion attribute value to the 2008.3.1125.35 )





4. Also checked in GAC, No telerik DLL is available/ installed in GAC.

5. Run the application . with the new settings.

Again found the same error (Multipe reference for telerik DLL )

Error:************************************************************************************************
Compiler Error Message: BC32206: The project currently contains references to more than one version of Telerik.Web.UI, a direct reference to version 2008.3.1125.35 and an indirect reference (through 'DotNetNuke.Web.UI.WebControls.DnnWindowManager') to version 2010.2.929.35. Change the direct reference to use version 2010.2.929.35 (or higher) of Telerik.Web.UI.

Source Error:



Line 30:
Line 31:
Line 32:
Line 33:

Line 34:


Source File: C:\centrum\CentumOnline\Default.aspx Line: 32
******************************************************************************************************


Please suggest .

 
New Post
2/6/2011 10:49 PM
 
I had the similar issue with the Telerik dll. But in my case it was a different problem and I thoght it might be worth sharing.
We had another .NET app running under the DNN folder as a seperate app. So in web.config we had

<configuration>
  <location path="." inheritInChildApplications="false">  
    <system.webServer>
     .....
    </system.webServer>
  </location>
</configuration>

After reviewing the Telerik install under  \Install\Module\Telerik_05.06.00_Install.zip\DotNetNuke.Telerik.Web.dnn  I found that the configuration node is

<node path="/configuration/system.web/httpHandlers" .....>

After change it to

<node path="/configuration/location/system.web/httpHandlers" ....>

Installation of module no londer fails and upgrade successed with no issues.
 
New Post
11/9/2011 12:03 AM
 
The only thing I had to do was to edit this line to include the correct version of the Telerik.web.ui.dll






I also hade to manually ftp the Telerik module as the dotnetnuke installation didnt unzip it. Thus the fault in the Dotnetnuke upgrading script is that it edit the web.config but doesnt unzip the Telerik_05.06.03_Install.zip file
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Reference required to assembly Telerik.Web.UIReference required to assembly Telerik.Web.UI


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