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
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Why System.Web.Extensions v.1.0.61025.0?Why System.Web.Extensions v.1.0.61025.0?
Previous
 
Next
New Post
5/8/2008 2:53 PM
 
Jon Seeley

www.seeleyware.com
Joined: 8/8/2006
Posts: 597

I'm curious why the instructions from Michael Washington tell us to use the System.Web.Extensions v.1.0.61025.0 instead of 3.5.0.0?  I have some controls (Telerik) that I've been using with ASP.NET 2.0 but I'd like to roll into using 3.5 for everything now and if I switch to their 3.5 version it requires System.Web.Extensions 3.5.0.0 to be referenced.  I've changed it in my web.config to reflect that and it works now and nothing else seems to have broken, but just trying to get some reasoning here in case there was a real reason why he was targeting the older System.Web.Extensions.

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
5/21/2008 1:58 AM
 
Wes Tatters


Wes Tatters's Avatar

Joined: 4/30/2004
Posts: 2155

At a guess michael may have been using a beta or rc version when that tutorial was created.

Im currently working in 2008 with the sp1 and .net 3.5sp1 beta and 3.5.0.0 works perfectly for all my testing.
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

Westa
 
New Post
5/21/2008 8:53 AM
 
Scott Stokes

www.adverageous.com
Joined: 4/25/2003
Posts: 110

I'm going to guess if you reference the 3.5.0 System.web.Extensions, your code will not work in sites running .net 2.0.

Although, I'm asleep at the moment and never tried..
 
New Post
5/21/2008 1:17 PM
 
Jon Seeley

www.seeleyware.com
Joined: 8/8/2006
Posts: 597

I'm fine with it not working on older sites since this is for our corporate intranet and I have full control over that.  What is weird is once I changed the reference to 3.5, I am getting a warning that 'asp:ScriptManager' is ambiguous.  Please modify the associated registration that is causing ambiguity and pick a new tag prefix. (this on an ASPX page in my module).

So I can change the TagPrefix and get it to work, but I don't really see why it won't work with the "asp" TagPrefix like the 2.0 version did.  Ideas?

*EDIT* -- apparently I had a few UserControls that were specifically targeting that version and I hadn't removed that reference.  I also added the assemblyBinding section under runtime at the bottom of my webconfig to hopefully forward all others that I may have forgotten.  Seems to do the trick.

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
8/27/2008 6:07 PM
 
Brian

Joined: 7/11/2008
Posts: 2

I found that switching the System.Web.Extensions version to 3.5.0.0 causes the Register button to stop working on an otherwise default install.     Not sure why yet - just thought I'd throw that out there.   Any ideas?    I'm on the new 3.5 SP1 framework, BTW

 
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Why System.Web.Extensions v.1.0.61025.0?Why System.Web.Extensions v.1.0.61025.0?


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