P1ST0LPETE
asked on
Trouble with AJAX Control Toolkit Installation
I am using Visual Web Developer 2008 Express Edition with the 3.5 Framework.
I recently downloaded the AJAX Control Toolkit via www.asp.net. Followed the instructions for installation and successfully loaded all the tools onto my toolbox in VWD. However, when I click and drag any of the new AJAX Control tools over onto my code, VWD doesn't recognize the cc1 tags and I get the following errors:
Warning 1 Unrecognized tag prefix or device filter 'cc1'.
Error 2 Unknown server tag 'cc1:accordion'.
I'm not sure what I've done wrong. I followed along with the installation video - went through it several times even. When I downloaded the AJAX Control Toolkit, I downloaded the "AjaxControlToolkit.zip" which is said to be "the full release package with complete source code to all controls, the test framework, VSI, and more."
Now then, in my searching I've found this solution here on experts-exchange:
https://www.experts-exchange.com/questions/23129669/AJAX-Control-Toolkit-Could-not-load-file-or-assembly-System-Web-Extension.html?sfQueryTermInfo=1+ajax+control+toolkit+work
I've searched and found the System.Web.Extensions.dll and added it to my bin file, still no luck. However I noticed in the above solution that the "ajax library" is mentioned as a seperate download. Is this "ajax library" not included in the AJAXControlToolket.zip ? If it's not, where should I install the library? If it is included in the AJAXControlToolket.zip, do you have any ideas as to what my issue may be?
Thanks for the help. Attached is simple application throwing the error, followed by web.config file.
I recently downloaded the AJAX Control Toolkit via www.asp.net. Followed the instructions for installation and successfully loaded all the tools onto my toolbox in VWD. However, when I click and drag any of the new AJAX Control tools over onto my code, VWD doesn't recognize the cc1 tags and I get the following errors:
Warning 1 Unrecognized tag prefix or device filter 'cc1'.
Error 2 Unknown server tag 'cc1:accordion'.
I'm not sure what I've done wrong. I followed along with the installation video - went through it several times even. When I downloaded the AJAX Control Toolkit, I downloaded the "AjaxControlToolkit.zip" which is said to be "the full release package with complete source code to all controls, the test framework, VSI, and more."
Now then, in my searching I've found this solution here on experts-exchange:
https://www.experts-exchange.com/questions/23129669/AJAX-Control-Toolkit-Could-not-load-file-or-assembly-System-Web-Extension.html?sfQueryTermInfo=1+ajax+control+toolkit+work
I've searched and found the System.Web.Extensions.dll and added it to my bin file, still no luck. However I noticed in the above solution that the "ajax library" is mentioned as a seperate download. Is this "ajax library" not included in the AJAXControlToolket.zip ? If it's not, where should I install the library? If it is included in the AJAXControlToolket.zip, do you have any ideas as to what my issue may be?
Thanks for the help. Attached is simple application throwing the error, followed by web.config file.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<div>
<cc1:accordion runat="server"></cc1:accordion>
</div>
</form>
</body>
</html>
================================================
================================================
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<appSettings/>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="false">
<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/></assemblies>
</compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<pages>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</controls>
</pages>
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
</system.web>
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="OptionInfer" value="true"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
</compilers>
</system.codedom>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<remove name="ScriptModule"/>
<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-Integrated"/>
<remove name="ScriptHandlerFactory"/>
<remove name="ScriptHandlerFactoryAppServices"/>
<remove name="ScriptResource"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</handlers>
</system.webServer>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<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>
</configuration>
ASKER
Well to the best of my knowledge I downloaded the 3.5 version, because I remember reading that if I already had the 3.5 framework installed, that I should download that version. However, it's possible I downloaded the wrong one. Is there a way that I could check which version I downloaded?
Also, I must have goofed with my copy/paste on the attached code above. The actual page looks like this: see attached.
When I drag one of the controls onto the work area, VWD automatically creates a bin folder and fills with with some 15-20 AjaxToolKit.dll files. It also creates the following line at the same time:
<%@ Register Assembly="AjaxControlToolk it" Namespace="AjaxControlTool kit" TagPrefix="cc1" %>
Also, I must have goofed with my copy/paste on the attached code above. The actual page looks like this: see attached.
When I drag one of the controls onto the work area, VWD automatically creates a bin folder and fills with with some 15-20 AjaxToolKit.dll files. It also creates the following line at the same time:
<%@ Register Assembly="AjaxControlToolk
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<div>
<cc1:accordion runat="server"></cc1:accordion>
</div>
</form>
</body>
</html>
Look at the file version for the AjaxControlToolkit.dll.
Hi P1ST0LPETE,
Try this also...
In your web.config file, under <pages><controls>, you have 2 <add tagPrefix="asp"....> elements (Lines 83 and 84). Add the following also as another element under it:
<add tagPrefix="asp" assembly="AjaxControlToolk it" namespace="AjaxControlTool kit"/>
If this works as expected, it won't add <%@ Register Assembly... tags on top of the page markup, instead it will use the normal "asp:" tag prefix for the toolkit controls too.
And I don't understand why you had to copy the System.Web.Extensions.dll into your bin folder.
See if you have AjaxControlToolkit, System.Web.Extensions, System.Web.Extensions.Desi gn etc under "References" of the Property Pages of the site (Right-Click on the website project's node in Solution explorer and select "Property Pages")
Hope that helps
Try this also...
In your web.config file, under <pages><controls>, you have 2 <add tagPrefix="asp"....> elements (Lines 83 and 84). Add the following also as another element under it:
<add tagPrefix="asp" assembly="AjaxControlToolk
If this works as expected, it won't add <%@ Register Assembly... tags on top of the page markup, instead it will use the normal "asp:" tag prefix for the toolkit controls too.
And I don't understand why you had to copy the System.Web.Extensions.dll into your bin folder.
See if you have AjaxControlToolkit, System.Web.Extensions, System.Web.Extensions.Desi
Hope that helps
ASKER
TheLernedOne:
I looked at the properties on the AjaxControlToolkit.dll and the version # is 3.0.20229.20843
Guganeshan:
I added <add tagPrefix="asp" assembly="AjaxControlToolk it" namespace="AjaxControlTool kit"/> to my web.config file.
Then deleted the <cc1:accordion> tag and the <%@ Regester Assembly.....TagPrefix="cc 1" %>.
Next dragged a new Accordion control over, and it placed it on the page as expected as <asp:Accordion>. However, I am now getting the error and warning that Element Accordion and server tag asp:Accordion are not known.
The reason why I coppied System.Web.Extensions.dll into the bin folder was because I just didn't know any better, and I was following the advice from the expert answer in the linked solution in my original post. I did go into Property Pages >> References, and this is what is listed:
Reference Name Type Version
AjaxControlToolkit BIN Auto Update
System.Core GAC 3.5.0.0
System.Data.DataSetExtensi ons GAC 3.5.0.0
System.Design GAC 2.0.0.0
System.Web.Extensions GAC 3.5.0.0
System.Web.Extensions.Desi gn GAC 3.5.0.0
System.Windows.Forms GAC 2.0.0.0
System.Xml.Linq GAC 3.5.0.0
So from the looks of this, I already had the System.Web.Extensions.dll applied to my website and didn't have to copy it into my Bin folder.
At any rate, things are still not working.
I looked at the properties on the AjaxControlToolkit.dll and the version # is 3.0.20229.20843
Guganeshan:
I added <add tagPrefix="asp" assembly="AjaxControlToolk
Then deleted the <cc1:accordion> tag and the <%@ Regester Assembly.....TagPrefix="cc
Next dragged a new Accordion control over, and it placed it on the page as expected as <asp:Accordion>. However, I am now getting the error and warning that Element Accordion and server tag asp:Accordion are not known.
The reason why I coppied System.Web.Extensions.dll into the bin folder was because I just didn't know any better, and I was following the advice from the expert answer in the linked solution in my original post. I did go into Property Pages >> References, and this is what is listed:
Reference Name Type Version
AjaxControlToolkit BIN Auto Update
System.Core GAC 3.5.0.0
System.Data.DataSetExtensi
System.Design GAC 2.0.0.0
System.Web.Extensions GAC 3.5.0.0
System.Web.Extensions.Desi
System.Windows.Forms GAC 2.0.0.0
System.Xml.Linq GAC 3.5.0.0
So from the looks of this, I already had the System.Web.Extensions.dll applied to my website and didn't have to copy it into my Bin folder.
At any rate, things are still not working.
Is the AjaxControlToolkit in the bin folder?
ASKER
"Is the AjaxControlToolkit in the bin folder?" - Yes.
ASKER
Infact, I didn't even have a bin folder, until I dragged and dropped my first ajax control from the ajaxcontroltoolkit onto the page. When ever I add my first ajax control from the controltoolkit on a new project, it takes a few seconds to add the bin folder, filled with all the AjaxControlToolkit .dll files.
Are you having problems with all the controls in the toolkit, or just the Accordion?
ASKER
Yeah, all of the AjaxControlToolkit controls are not working.
ASKER
I would think there has to be something I'm not doing correctly. I have tried to install the AjaxControlToolkit on 3 different computers: Work Desktop, Home Desktop, and Laptop. All of which have windows xp, Visual Web Developer 2008 Express Edition, 3.5 Framework, AND all have the same problem with the AjaxControlToolkit.
Steps I took with 2008 VWD:
1) Added the controls from AjaxControlToolkit.dll (3.0.20229.0) to the tool box.
2) Added a TextBox control.
3) Clicked on the SmartTag for the TextBox control to add an extender. Selected the SliderExtender.
4) AjaxControlToolkit.dll and all the language resources added to the bin folder.
5) Ran the web site in the IDE, and it worked as advertised.
1) Added the controls from AjaxControlToolkit.dll (3.0.20229.0) to the tool box.
2) Added a TextBox control.
3) Clicked on the SmartTag for the TextBox control to add an extender. Selected the SliderExtender.
4) AjaxControlToolkit.dll and all the language resources added to the bin folder.
5) Ran the web site in the IDE, and it worked as advertised.
ASKER
Ok, I Just created a new website. Added a TextBox. Clicked on the TextBox and then clicked on the arrow to add an extender. Extender list came up with all the available options. Clicked on Slider Extender. Extender was added. Switch back to code view and got an error on the "cc1" tag prefix again, followed by a bunch of warnings on all the attributes within the extenter tag.
- - - - - - - - - - - - - - - - - - - - - - - - - -
I've been reviewing the setup instructions found at http://www.asp.net/ajax/ajaxcontroltoolkit/samples/Walkthrough/Setup.aspx .
On step #1 under "Configure Visual Studio 2005 and Visual Web Developer", I don't have a template called "ASP.NET AJAX Web Site" under "My Templates". When I installed the AjaxControlToolkit, I just skipped that step, and did steps 2-5.
- - - - - - - - - - - - - - - - - - - - - - - - - -
I've been reviewing the setup instructions found at http://www.asp.net/ajax/ajaxcontroltoolkit/samples/Walkthrough/Setup.aspx .
On step #1 under "Configure Visual Studio 2005 and Visual Web Developer", I don't have a template called "ASP.NET AJAX Web Site" under "My Templates". When I installed the AjaxControlToolkit, I just skipped that step, and did steps 2-5.
Did you do these steps (I didn't)?
Installing AJAX Control Toolkit Templates
1) In the folder where you installed the AJAX Control Toolkit package, you will find a folder called "AjaxControlExtender" with a file called "AjaxControlExtender.vsi" inside it - double-click AjaxControlExtender.vsi to install it
2) Choose which templates you would like to install, then click "Next", then "Yes" to allow the unsigned content (note: as a public project, this content can't be signed by Microsoft), then "Finish"
3) You have now installed the templates are ready to create your own Toolkit-based web site or ASP.NET AJAX Extenders!
Installing AJAX Control Toolkit Templates
1) In the folder where you installed the AJAX Control Toolkit package, you will find a folder called "AjaxControlExtender" with a file called "AjaxControlExtender.vsi" inside it - double-click AjaxControlExtender.vsi to install it
2) Choose which templates you would like to install, then click "Next", then "Yes" to allow the unsigned content (note: as a public project, this content can't be signed by Microsoft), then "Finish"
3) You have now installed the templates are ready to create your own Toolkit-based web site or ASP.NET AJAX Extenders!
You might want to remove all the items from the tool box, and re-add them.
ASKER
Yeah, followed the steps for the AJAX Control Toolket Templates too, but I still don't have any templates.
Also, I deleted my entire tab for the toolkit controls, and re-added them. Still no luck. This is just frustrating. At home I've also downloaded the asp video controls from www.aspnet-media.com, and I'm having the exact same problems with those control tools.
Also, I deleted my entire tab for the toolkit controls, and re-added them. Still no luck. This is just frustrating. At home I've also downloaded the asp video controls from www.aspnet-media.com, and I'm having the exact same problems with those control tools.
ASKER
Correction to above link: www.aspnetmedia.com
I believe that you are having the same problem as here:
https://www.experts-exchange.com/questions/23367389/Visual-Studio-2008-not-recognizing-Ajax-Control-Toolkit-3-5.html
I just need a placeholder so that I can help both.
https://www.experts-exchange.com/questions/23367389/Visual-Studio-2008-not-recognizing-Ajax-Control-Toolkit-3-5.html
I just need a placeholder so that I can help both.
ASKER
Yes, that seems to be the exact same problem.
I see we are having the exact same issue. (Maybe we can figure this out together). The main difference I see between our issues is that one of us is using express and the other the full version. This makes me wonder if there is an issue with this version of the toolkit.
I have the express 2008 version installed on my home machine and I checked it out last night. It does work okay, but I noticed the toolkit was the previous version; not the version we are both trying to install. I am going to re-install VS2008 again and see what happens.
I have the express 2008 version installed on my home machine and I checked it out last night. It does work okay, but I noticed the toolkit was the previous version; not the version we are both trying to install. I am going to re-install VS2008 again and see what happens.
The one thing that I see in common is that you both installed the .vsi template package, which I didn't, and it works fine for me. I don't see where that would be a problem, but you just never know.
ASKER
I have noticed that when I load the AjaxControlToolkit.sln solution file in VWD the sample pages work just fine, not issuing any errors. I can add controls and rebuild the page just fine, and then view it on my machine via the virtual web server that VWD creates. Im trying to figure out now what configurations are different from the solution and one of my newly created projects.
I have noticed the exact same thing. When I load the source solution it works fine. Have you tried publishing a test website to a server? I'm wondering if this is an issue related to Intellisense.
I think we can get a clue if we can see P1ST0LPETE's web.config file (without the sensitive info)
It might be how the reference is added to the web.config file in the <assemblies> section.
The only thing is I compared the AjaxControlToolkit web.config file with my test project web.config and they were identical. I wondered if I needed an entry relating to the toolkit in there, but it doesn't seem to be necessary.
Okay, I got it to work from another post I had on ASP.NET forums. The person recommended I add the extender in a different order.
Try this:
- Create a new regular 3.5 website
- Go to the design side of the starting default.aspx page.
- Add something simple like a Panel
- Now from the smart control of the Panel, choose "add extender" and choose a drop shadow.
- The AjaxControlToolkit.DLL will auto-add to the BIN folder.
- Now add the script manager and test run the site.
Mine worked this time... don't know why it wouldn't work the other way. I've used the old method adding the .dll file manually a dozen times in the past.
Try this:
- Create a new regular 3.5 website
- Go to the design side of the starting default.aspx page.
- Add something simple like a Panel
- Now from the smart control of the Panel, choose "add extender" and choose a drop shadow.
- The AjaxControlToolkit.DLL will auto-add to the BIN folder.
- Now add the script manager and test run the site.
Mine worked this time... don't know why it wouldn't work the other way. I've used the old method adding the .dll file manually a dozen times in the past.
ASKER
I tried your method cciservices - didn't work for me. Attached is my web.config file after following cciservices method. I also compared my web.config file to that of the AjaxControlToolkit.sln's web.config file - couldn't find one spot where they were different.
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<appSettings/>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="false">
<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/></assemblies>
</compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<pages>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</controls>
</pages>
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
</system.web>
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="OptionInfer" value="true"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
</compilers>
</system.codedom>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<remove name="ScriptModule"/>
<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-Integrated"/>
<remove name="ScriptHandlerFactory"/>
<remove name="ScriptHandlerFactoryAppServices"/>
<remove name="ScriptResource"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</handlers>
</system.webServer>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<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>
</configuration>
P1ST0LPETE:...
I created a new website and replaced the web.config file with your web.config file. It works once I add the ajax control toolkit. (I always add the tag prefix to the web.config though)
There's one more thing I have to ask you to check.
Visual Studio 2008 creates the new website with a reference to .NET Framework 2.0 for me (Didn't drill into the details why). So once I converted the project to 3.5, there was no problem for me (before that, the extenders in the toolbox were not visible for me). I'm not sure about Visual Web Developer though
So just try this...
1. Right-Click on the website project's node in Solution explorer and select "Property Pages"
2. Select "Build"
3. Make sure the target framework is ".NET Framework 3.5"
[Note: I tested with the latest AjaxControlToolkit version 3.0.20229.0 for .NET framework 3.5]
Hope that helps
I created a new website and replaced the web.config file with your web.config file. It works once I add the ajax control toolkit. (I always add the tag prefix to the web.config though)
There's one more thing I have to ask you to check.
Visual Studio 2008 creates the new website with a reference to .NET Framework 2.0 for me (Didn't drill into the details why). So once I converted the project to 3.5, there was no problem for me (before that, the extenders in the toolbox were not visible for me). I'm not sure about Visual Web Developer though
So just try this...
1. Right-Click on the website project's node in Solution explorer and select "Property Pages"
2. Select "Build"
3. Make sure the target framework is ".NET Framework 3.5"
[Note: I tested with the latest AjaxControlToolkit version 3.0.20229.0 for .NET framework 3.5]
Hope that helps
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Follow up to my previous post...
Here is a better explanation:
http://forums.asp.net/p/1222837/2325406.aspx
Here is a better explanation:
http://forums.asp.net/p/1222837/2325406.aspx
ASKER
OMG. I just about fell out of my chair here at work, when it actually worked. Both here at work and at home I've been connecting to the web servers via a network share connection. Man, I've been battling this issue for weeks - what a relief to finally have it working. If you lived near by, I'd have to buy you lunch.
ASKER
Thanks for your research and help.
Thats great to hear. Now the issue I'm having is that I NEED to work off a shared network folder, so I am try to change the Code Assembly security to allow this....
Here is my new post: https://www.experts-exchange.com/questions/23377252/AJAX-Control-Toolkit-3-5-from-network-share.html
Here is my new post: https://www.experts-exchange.com/questions/23377252/AJAX-Control-Toolkit-3-5-from-network-share.html
In case anyone comes across this question, here is how to add a share as a trusted location. This will fix the "Unrecognized tag prefix" error:
http://blogs.msdn.com/shawnfa/archive/2004/12/30/344554.aspx
http://blogs.msdn.com/shawnfa/archive/2004/12/30/344554.aspx
2) I don't see any line like this:
<%@ Register Assembly="AjaxControlToolk