AJAX problem
AJAX problem
AJAX problem
AJAX problem
AJAX problem
AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem
AJAX problem AJAX problem
AJAX problem
Go Back  Xtreme Visual Basic Talk > > > AJAX problem


Reply
 
Thread Tools Display Modes
  #1  
Old 04-04-2007, 02:17 PM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default AJAX problem


ok, I dunno if this is the right place to post this. I'll let the moderators decide.

I have inherited a project that uses an older version of Ajax, and I have on my machine Ajax version 1.

This line:

Quote:
<asp:ScriptManager runat="server" id="ScriptManager1" EnablePartialRendering="true" />
is giving me the error:

Quote:
Error 1 Element 'ScriptManager' is not a known element. This can occur if there is a compilation error in the Web site.
I am 60% positive that this has to do with the versions of Ajax.
How do I fix this?
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #2  
Old 04-05-2007, 07:42 AM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

please...??
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #3  
Old 04-05-2007, 08:32 AM
DeadalusAJAX problem Deadalus is offline
Promising Talent

Retired Moderator
* Guru *
 
Join Date: May 2002
Location: Brussels
Posts: 3,601
Default

I don't see why that line would not work with the Ajax Extensions 1.0. Are you sure you have the Ajax extensions properly installed? Do they (and the Scriptmanager component in particular) show up in your toolbox?
Reply With Quote
  #4  
Old 04-05-2007, 08:39 AM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

I have the exact same thoughts. Yes Ajax and the ScriptManager is visible on my toolbox and was properly installed. The only thing I can see is that the project was created using an older(beta) version of AJAX and my machine has the full version.

I have tried:
1. closing all windows, open the master page, open the page that shows the error and then RESET TOOLBOX, drop another ScriptManager and delete the first one. -- this is what I usually did before but does not work this time around.
2. downloading Microsoft.Web.Extensions.Design.dll and Microsoft.Web.Extensions.dll and used GACUTLIS to add them in the GAC but still the error remains.

Right now I am considering this issue at medium priority because I can still edit the pages but only through the markup. Can't see the page in design view.

Thank you Daedalus, I hope my reply helps.
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #5  
Old 04-05-2007, 08:53 PM
HardCode's Avatar
HardCodeAJAX problem HardCode is offline
Ultimate Contributor

Forum Leader
* Expert *
 
Join Date: Feb 2004
Location: New Jersey
Posts: 3,339
Default

Did you uninstall the Beta AJAX version first? I just installed it today, too, and the docs said to make sure you both: uninstall beta AJAX and install VS 2005 SP1.
__________________
DON'T CLICK HERE

Useful forum tags: [VB][/VB], [CODE][/CODE], [HTML][/HTML]
Reply With Quote
  #6  
Old 04-06-2007, 07:14 AM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

No I did not have the beta before. This machine I am using has never been installed with AJAX beta, only Version 1. And the project I am working on uses beta version of AJAX. I think this is the conflict here.
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #7  
Old 04-06-2007, 01:25 PM
MKoslof's Avatar
MKoslofAJAX problem MKoslof is offline
Cum Grano Salis

Retired Moderator
* Guru *
 
Join Date: Jul 2002
Location: Baltimore, Maryland
Posts: 14,636
Default

Quote:
No I did not have the beta before. This machine I am using has never been installed with AJAX beta, only Version 1. And the project I am working on uses beta version of AJAX. I think this is the conflict here.
So your development machine has Version 1 of the AJAX framework. This project is using a beta version of AJAX. So why don't you simply update the project to use version 1? You have the compliant software on your development machine, so upgrade the project.

Now, if the problem is you *can't* upgrade the project, there is something in the project which is holding old references, maybe compiled assemblies, your imports or references are off - - that isn't easy to guess off hand.

How complicated is this AJAX component? Can you simply re-write it using your AJAX v1.0 framework?
__________________
"Artificial Intelligence is no match for natural stupidity." ~unknown
Reply With Quote
  #8  
Old 04-06-2007, 01:30 PM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

The Ajax component is a simulated dropdown-list/autocomplete textbox but scattered all over the project. Many pages use the control.

Caveman question:
What does "upgrading" a project mean? It will come from VS2005 to VS2005. A lateral upgrade? I am unsure of an AJAX upgrade(haven't touched google yet) also.
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #9  
Old 04-06-2007, 01:37 PM
MKoslof's Avatar
MKoslofAJAX problem MKoslof is offline
Cum Grano Salis

Retired Moderator
* Guru *
 
Join Date: Jul 2002
Location: Baltimore, Maryland
Posts: 14,636
Default

No, you said the project is using a Beta version of AJAX. Your development machine is using Version 1. You aren't upgrading Visual Studio, basically you are ripping out the older AJAX functionality and hooking up "new" AJAX functionality using the version of AJAX on your development computer.

If it is just a standard user control, meaning it is being reused on multiple pages, why not re-write the single user control?
__________________
"Artificial Intelligence is no match for natural stupidity." ~unknown
Reply With Quote
  #10  
Old 04-06-2007, 01:42 PM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

Re-writing the control(which I consider as "not broke"), although guaranteed to solve the secondary situation of being able to continue development, in my opinion does not solve the primary issue I have shared.

That when a project who has a component designed with a beta version of Ajax is opened by a machine with the release version of Aajx, an error will occur.

Thank you for the insight and I want to share this too:
Another thing I noticed is that the IDE tags a whole lot of markup attributes as "Obsolete" like Border, Type, etc.. I think the problem is connected and may lie in Intelisense. What do you think?
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
  #11  
Old 04-06-2007, 01:58 PM
MKoslof's Avatar
MKoslofAJAX problem MKoslof is offline
Cum Grano Salis

Retired Moderator
* Guru *
 
Join Date: Jul 2002
Location: Baltimore, Maryland
Posts: 14,636
Default

Huh? Obsolete means the current code is using outdated technology. Microsoft doesn't guarantee that obsolete code will be supported as newer versions are released. This is standard and it has nothing to do with intellisense...that is simply a feature of the IDE.

The primary issue you have is trying to piece together why an outdated piece of code isn't working or compiling in a different version. That has EVERYTHING to do with upgrading.

Was this component originally written in VS 2003 or 2005? If you have a different version of AJAX installed on a given machine and errors occur, that basically tells you where the problem is. Is the Beta version of AJAX not compliant with release versions? Typically that IS the case with beta software - - there is no backwards compatibility with beta software and release software.
__________________
"Artificial Intelligence is no match for natural stupidity." ~unknown
Reply With Quote
  #12  
Old 04-06-2007, 02:45 PM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

My bad. The IDE underlines some markup tags like Border as being considered outdated.

The old project is written in VS2005 also.

And I think I have found the solution:

The assembly name of ASP.NET AJAX changed from Microsoft.Web.Extensions.dll to System.Web.Extensions.dll. I think this is because AJAX will be considered a permanent fixture in the framework?

Also, the namespace of the server-side features of ASP.NET AJAX changed from Microsoft.Web to System.Web.

With Windows XP you do this by deleting all files in this directory: c:\Document and Settings\[YourUserName]\Application Data\Microsoft\VisualStudio\8.0\ReflectedSchemas

update. I found this link right after I finished my editing.

But the good news is that the fix I chanced upon happened because my machine has VS ServicePack 1 AND am using a MasterPage.
__________________
Pinoy ako.. ipinagmamalaki ko.

Last edited by wayneph; 04-06-2007 at 02:56 PM.
Reply With Quote
  #13  
Old 04-06-2007, 02:56 PM
wayneph's Avatar
waynephAJAX problem wayneph is offline
Web Junkie

Retired Moderator
* Expert *
 
Join Date: Apr 2004
Location: D/FW, Texas, USA
Posts: 8,393
Default

That sounds like it will at least partially solve your issues. You'll still need to make sure that the code is fixed to look at the new Namespaces.

Also, things like Border are showing up as obsolete because it's depreciated in the XHTML standard. You should be using CSS instead.

i.e: style="border:1px solid black"
__________________
-- wayne, MSSM Retired
> SELECT * FROM users WHERE clue > 0
0 rows returned
Reply With Quote
  #14  
Old 04-06-2007, 03:05 PM
Eduardo Lorenzo's Avatar
Eduardo Lorenzo Eduardo Lorenzo is offline
Senior Contributor
 
Join Date: Jun 2006
Location: Manila, Philippines
Posts: 846
Default

Well it did solve my problem partially. Am in the process of re-examining the code now.
__________________
Pinoy ako.. ipinagmamalaki ko.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Forum Jump

Advertisement:





Free Publications
The ASP.NET 2.0 Anthology
101 Essential Tips, Tricks & Hacks - Free 156 Page Preview. Learn the most practical features and best approaches for ASP.NET.
subscribe
Programmers Heaven C# School Book -Free 338 Page eBook
The Programmers Heaven C# School book covers the .NET framework and the C# language.
subscribe
Build Your Own ASP.NET 3.5 Web Site Using C# & VB, 3rd Edition - Free 219 Page Preview!
This comprehensive step-by-step guide will help get your database-driven ASP.NET web site up and running in no time..
subscribe
AJAX problem
AJAX problem
AJAX problem AJAX problem
AJAX problem
AJAX problem
AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem AJAX problem
AJAX problem
AJAX problem
 
AJAX problem
AJAX problem
 
-->