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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ....Net Framework 3.5 Upgrade Help.Net Framework 3.5 Upgrade Help
Previous
 
Next
New Post
2/5/2008 1:22 PM
 

Okay, this should be easy, as I know I must be overlooking something simple.

I upgraded my site to DNN 4.8 and then installed .Net Framework 3.5 on my server.

To test out the 3.5 Framework, I added a new asp:ListView Control to a module, which of course added the following declaration at the top of ascx control:
@ Register Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI.WebControls" TagPrefix="asp" 

After navigating to a page this module is on, my web.config was automatically modified and my site crash with the following error:
'ScriptServiceAttribute' is ambiguous in the namespace 'System.Web.Script.Services'
(which was referenced from a webservice I have in my App_Code directory.)

I understand the error is a conflict of namespace between System.Web.Extensions, Version=3.5x and System.Web.Extensions, Version=3.1x but how do I correct the errors?

Do I just remove one of the following lines from the web.config?
add assembly ="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/ 
add assembly ="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/


Or is there documentation on how to upgrade your Dotnetnuke modules code to the 3.5 framework?

Thanks for any help anyone can give, as I couldn't find any documentation elsewere...

 

 

 
New Post
2/5/2008 5:23 PM
 

Okay,  I got it figured out.

I had a clean version of DNN 4.8 and ASP.NET 3.5 running vista on my laptop, so I just used  that web.config and
I just replaced every mention of System.Web.Extensions version 1 in my sites web.config with the version 3.5 settings from vista.

I replaced the setting under the following areas

httpModules
httpHandlers
assemblies
controls
dependentAssembly

and system.webServer in case I ever move the site to IIS7

Everything is working great now, hope this helps someone. I noticed it is in google's index already

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ....Net Framework 3.5 Upgrade Help.Net Framework 3.5 Upgrade Help


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