AJAX :: Error : CS1705 Running Ajaxcontroltoolkit V 3.5.40412.0
Nov 18, 2010
I'm developing on an existing software (PLM) with visual studio 2008, a new ascx page.
Microsoft .NET Framework use by the soft is : 2.0.50727.1433 and ASP.NET version use by the soft is : 2.0.50727.1433 too.
On my server, I've installed Framework 3.5 and I use Ajax Control tool kit version 3.5.40412.0.
I've got a similar problem than other people, but I can't find any solution.I've got the Error message when I want to load a page : CS1705: Assembly AjaxControlKit version 3.5.40412.0 [...] use System.Web.extensions Version 3.5.0.0 [...] which have a higher version than Assembly System.Web.Extensions Version 1.0.61025.0
On my server in folder C:windowsAssembly, I have System.Web.extensions Version 3.5.0.0 and System.Web.Extensions Version 1.0.61025.0 so in theory it can work no ?In my webconfig file I try to add this code :
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31BF3856AD364E35"/> [code]....]
View 2 Replies
Similar Messages:
Feb 15, 2011
We get this Warning in the Event Log from time to time. It seems to crasch our web so an iisreset is required.I have checked the version of AjaxControlToolkit that we use - and it is the version it says it needs. So what should I do?
Exception information:
Exception type: InvalidOperationException
Exception message: The requested script resource 'Common.Common.js' requires version 'AjaxControlToolkit, Version=4.1.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' of the ASP.NET AJAX Framework. To use this resource, make sure that the application references version 'AjaxControlToolkit, Version=4.1.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e'.
View 7 Replies
Jul 2, 2010
I develop an ASP.NET 2.0 with VS 2008, VB.NET, and sometime a get this exception when web application is launching.
Message Parser Error: Could not load file or assembly 'AjaxControlToolkit, Version = 3.5.40412.0, Culture = neutral, PublicKeyToken = 28f01b0e84b6d53e' or one of its dependencies.The definition from the assembly manifest does not match the assembly reference. (Exception from HRESULT: 0x80131040)
To solve this problem, I need to regenerate the project. I would like to understand why this error append sometime. I try to check the version referenced in project property, try to check the version attribute on Web.Config :
<pages theme="Formulaires" validateRequest="false" styleSheetTheme="Formulaires" enableEventValidation="false" enableViewStateMac="false">
<controls>
<add tagPrefix="ajaxToolkit" namespace="AjaxControlToolkit" assembly="AjaxControlToolkit, Version=3.5.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e" />
<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>
<namespaces>
<clear/>
<add namespace="System"/>
<add namespace="System.Collections"/>
<add namespace="System.Collections.Specialized"/>
<add namespace="System.Configuration"/>
<add namespace="System.Text"/>
<add namespace="System.Text.RegularExpressions"/>
<add namespace="System.Web"/>
<add namespace="System.Web.Caching"/>
<add namespace="System.Web.SessionState"/>
<add namespace="System.Web.Security"/>
<add namespace="System.Web.Profile"/>
<add namespace="System.Web.UI"/>
<add namespace="System.Web.UI.WebControls"/>
<add namespace="System.Web.UI.WebControls.WebParts"/>
<add namespace="System.Web.UI.HtmlControls"/>
</namespaces>
</pages>
It the correct version... i don't understand about this problem.
View 2 Replies
Jan 5, 2011
i am working in webapplication in asp.net using c#.I have a problem that currently i am using ajaxcontroltoolkit version 3.0.20820.0 but in this toolkit i don't have Editor Ajax control so i want to upgrade it with new version ajaxcontroltoolkit version 3.5.40412.2
When i upgrade it then my old ajax control is not working like validatorcalloutextender and requiredfieldvalidator etc.
so please tell me how can i upgrade ajaxcontroltoolkit version from 3.0.20820.0 to version 3.5.40412.2
i also use in web.config file but not successfull.
View 1 Replies
Sep 21, 2010
i use script manager and i do what ever the tuterials say for adding ajax toolkit .
i want to use button confirm extender but when the page wants to load give me this error:
Error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll.
View 2 Replies
Mar 12, 2010
All my web applications are using AjaxControlToolkit 1.0 version. But I have one third party website that is using AjaxControlToolkit 3.5. When I run that third party website I got the following error.
The type 'AjaxControlToolkit.DropDownExtender' exists in both 'c:WINDOWSassemblyGAC_MSILAjaxControlToolkit3.5.11119.20050__28f01b0e84b6d53eAjaxControlToolkit.dll' and 'c:WINDOWSassemblyGAC_MSILAjaxControlToolkit1.0.20229.20821__28f01b0e84b6d53eAjaxControlToolkit.dll'
I do have assembly reference at server level web.config
<add assembly="AjaxControlToolkit, Version=1.0.20229.20821, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e" />
View 9 Replies
May 2, 2010
I was working with the previous version of the AjaxControlToolkit (I had the source project in my solution, just in case I needed to debug something) and everything worked ok, now I've downloaded the lastest build (40412) and I've choosen to remove that project and only use the binaries (of 40412). I added this line in the web.config (inside <controls>) to have it prepared for all the pages, and avoid the need to use the @register in each one of them <add namespace="AjaxControlToolkit" assembly="AjaxControlToolkit" tagPrefix="ajaxtoolkit"/>
Now, only have the binaries I think I should used
<add tagPrefix="ajaxToolkit" namespace="AjaxControlToolkit" assembly="AjaxControlToolkit, Version=3.5.40412.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
and inside <assemblies> this line
<add assembly="AjaxControlToolkit, Version=3.5.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e"/>
I don't know what should I write as PublicKeyToken, I'm getting Cannot resolve symbol 'AjaxControlToolkit' and, of course, my UserControls that use the AjaxControlToolkit are giving me error.
View 13 Replies
Nov 3, 2010
I coverted a VS 2008 project to VS 2010. I then downloaded and installed the AjaxControlToolkit for .net 4. When I run in debug mode I get an the following error. The code worked in VS 2008 .net 3.5. No Source Available There is no source code available for the current location. Call stack location:
AjaxControlToolKitDLL!AjaxControlToolkit.ToolkitScriptManager.OnLoad(System.EventArgs e) Line157
Source file information:
Locating source for 'd:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs'. Checksum: MD5 {c1 d2 e2 8c cd 4b 65 11 35 53 7f f5 e3 3b 76 58}
The file 'd:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs' does not exist.
Looking in script documents for 'd:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs'...
Looking in the projects for 'd:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs'.
The file was not found in a project.
Looking in directory 'C:Program Files (x86)Microsoft Visual Studio 9.0VCcrtsrc'...
Looking in directory 'C:Program Files (x86)Microsoft Visual Studio 9.0VCatlmfcsrcmfc'...
Looking in directory 'C:Program Files (x86)Microsoft Visual Studio 9.0VCatlmfcsrcatl'...
Looking in directory 'C:Program Files (x86)Microsoft Visual Studio 9.0VCatlmfcinclude'...
Looking in directory 'C:'...
The debug source files settings for the active solution indicate that the debugger will not ask the user to find the file:d:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs.
The debugger could not locate the source file 'd:hgactServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs'.
View 1 Replies
Apr 8, 2010
trying to get the latest version of ACT I have (3.0.31106) working with a VS 2010 website, targetting .Net 4.0.
I have researched this and can't find a definitive answer.
I was using the AutoComplete Extender with no problems in VS2008 (ACT version 3.0.30512.1).
In creating this new VS2010 website I thought I ought to also check and get the latest version of the ACT.
Now, when running the new website I get the error other people get,
AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the AjaxScriptManager in System.Web.Ajax.dll, or use the ToolkitScriptManager in AjaxControlToolkit.dll.
What is the best approach here? I don't see the point ofusing the ToolkitScriptManager when the website already has the regular v4.0 ScriptManager.
I seem to have resolved this - fingers crossed - by downloading source version 49157 and then opening the .Net4 soultion file and building in VS2010. Then I got the AjaxControlToolkit.dll file from this project for use in my new website. This works fine now (for the autocomplete extender, at least).
View 5 Replies
Oct 29, 2010
I want to disable past dates, so i modified AjaxControlToolkit.dll and named as "Actkit.dll".
View 1 Replies
Sep 24, 2010
I am a bit new to ASP.Net Ajax and as such new to Ajax itself. I have a site which uses ASP.Net Ajax. It used the version AjaxControlToolkit version 3.0.30512.0. I have now changed it to version 3.5.40412.2 by deleting the old reference and adding a reference to the latest one . I build the soultion and everything appears fine witjhout any errors. But the site fails to load showing a yellow page with the message AjaxControlToolkit Version="3.5.40412.2" missing reference to 'AjaxControlToolkit.ExtenderBase.Base Scripts.js.BaseScripts.js'. What does this mean ?
View 2 Replies
Sep 6, 2010
I have a VS2010 Web Application that uses the AjaxControlToolkit. I am able to build the Debug configuration. When I build the release configuration I get the following error message: Error 89 Could not load file or assembly 'file:///S:My CodeLibrariesACTMay 2010AjaxControlToolkit.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) S:My CodeEZFishingEZFishingEZFishingSGEN EZFishing
The location of the file is correct, and I just downloaded and unzipped there the Ajax CT. I have always built this app correctly before upgrading to VS2010 and ACT May 2010.
View 3 Replies
Jan 14, 2011
Im am getting the following error:
Microsoft JScript runtime error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the AjaxScriptManager in System.Web.Ajax.dll, or use the ToolkitScriptManager in AjaxControlToolkit.dll.
I am using ASP.Net 4 and the AjaxControlToolkit .net 4 dll. On my page I am using the ToolkitScriptManager.What I don't understand is that it works without any issue on my development machine in Visual Studio and if I publish it to IIS on that machine. If I run it on another machine I got it also works without any issue. When I copy the published application to my web hosting provider, I am getting this issue.I was getting a SecurityException initially when the site loaded the AjaxToolkit assembly, but now that seems to have just gone away, but I still get this issue.
View 4 Replies
Mar 22, 2010
I am getting the above error, but i am not sure whats wrong with my code.
[Code]....
View 2 Replies
Oct 15, 2010
Moved our web application from W2003 & IIS6 to W2008 R2 & IIS7.5 . One of the first things we discovered was to set the Application Pool in "Classic" mode. However we are still not out of the woods. We are having a AjaxControlToolKit error. I have attached a screenshot but in summary, the first line of code referring to the AjaxControlToolKit is flagged in error, Type.registerNamespace('AjaxControlToolkit'); The Debugger throws the error text below: 'Type' is undefined Default.aspx?
_TSM_HiddenField_=ScriptManager1_Hidd enField&_TSM_CombinedScripts_=%3b%3bAjaxControlToo lkit%2c+Version%3d1.0.20229.26116%2c+Culture%3dneu tral%2c+PublicKeyToken%3d28f01b0e84b6d53e%3aen-US%3a63cfabab-51ed-48ea-9a51-d25d550c85e3%3ae2e86ef9%3a9ea3f0e2%3a9e8e87e9%3a1d f13a87%3a4c9865be%3aba594826%3a757f92c2%3a3858419b %3a96741c43%3ac4c00916%3ac7c04611%3acd120801%3a38e c41c0,
line 21 character 1I have made sure that AjaxControlToolKit.dll (ver 1.0.20229) is in the Bin folder of my website.
<pages>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add namespace="AjaxControlToolkit" assembly="AjaxControlToolkit" tagPrefix="ajaxToolkit" />
</controls>
</pages>
Entire web.config is in attacment also. I am not sure what else has to happen to move to the newer Microsoft platforms?
View 3 Replies
May 19, 2010
I just downloaded the latest AjaxControlToolKit.dll (3.5.40412.0), and update it in my old project. When I compile the project, it shows sucessful. However, when I used my Customized Calendar, it got "AjaxControlToolKit Undefined"
ps: my old project is developed under AjaxControlToolKit.dll (3.0.20820.16598) . // README
View 1 Replies
Nov 5, 2010
Looks like there aren't a lot of users using the Ajax Control Toolkit 40412 and the Microsoft Microsoft Ajax CDN because I can't find any information on how to get the MicrosoftAjax.js and MicrosoftAjaxWebForms.js files to be linked to the CDN.
First issue:Ajax Control Toolkit 40412 seems to be using its own customized version of MicrosoftAjax.js and MicrosoftAjaxWebForms.js. Toolkit's version
is 4.1.40412.2, while the version that come with ASP.NET Ajax 4 is 4.0.30205.0. By default when using the toolkit the version is swapped to the toolkit's version. While the ASP.NET Ajax 4 version is hosted on the CDN (http://www.asp.net/ajaxlibrary/CDNAjax4.ashx)
the version with the Toolkit is not (http://www.asp.net/ajaxlibrary/CDNACT40412.ashx), which doesn't make any sense because all the other files are hosted. Therefore, a CDN version of MicrosoftAjax.js and MicrosoftAjaxWebForms.js is UNAVAILABLE when using the Ajax Control Toolkit 40412.
Second Issue:Why not use the ASP.NET Ajax 4 version of the the MicrosoftAjax.js, after all its version 4. The version can be swapped out by adding a Script Resource Mapping to the Application_Start event in the Global.asax.cs.
void Application_Start(object sender, EventArgs e)
{
ScriptManager.ScriptResourceMapping.AddDefinition("MicrosoftAjax.js", new ScriptResourceDefinition
{
Path = "~/Scripts/MicrosoftAjax.js", [code]....
However, when the version is changed to the ASP.NET Ajax 4 version the following error is given:
"AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll."
It doesn't matter if you are using the ToolkitScriptManager or ScriptManager you will always get this error when not using the version of
MicrosoftAjax.js that comes with the AjaxControlToolkit.So how can one use the Microsoft Ajax CDN for the MicrosoftAjax.js and MicrosoftAjaxWebForms.js with ASP.NET Ajax 4 & Ajax Control Toolkit 40412?
One other note. The new attribute EnableCdn="true" is of course rendered completely useless when using the Ajax Control Toolkit because the idea is that the MicrosoftAjax.js and MicrosoftAjaxWebForms.js files would then be linked by references to the CDN. This does not happen with the Toolkit because as described the Toolkit replaces the those files with its own. I was very surprised to find out that all my excitement about having CDN support was made void when I included the Toolkit in my project.
View 6 Replies
Jun 2, 2010
using 40412 in VS2010, I can't get reorderlist to work - can't pick any items up and move them around in any browser. sample site works fine, and I even tried referencing the dll from the bin directory there with no luck. tried running some code that binds data manually from a working project that uses a previous release and all I get is a regular list. converted data source to a sqldatasource and still no dice.
one oddity I do see between my non-working project and the other working examples (sample site and my older project) is that the generated list item div IDs are identical in my project, while the working examples all have unique IDs generated, ie:
non-working project: <li id="ReorderList1" style="vertical-align:middle;"> (all LIs identical)
working example (40412 sample site): ><li id="ctl00_SampleContent_ReorderList1__rli5" style="vertical-align:middle;"> (each line has unique suffix - in this case __rli5)
View 4 Replies
Aug 6, 2010
Im having problem with the newest release of Ajax Control Toolkit under .NET 3.5
I downloaded source code from AjaxControlToolkit.Source.zip and compiled it under .NET 3.5
Then i made simple web application:
[Code]....
It failed to run with my compiled version of ACT, im having an error:"Line: 160 Error: '$common' is null or not an object"
in AsyncFileUpload.AsyncFileUpload.debug.js and then:
"Line: 22 Error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll." in
AsyncFileUpload.AsyncFileUpload.debug.js" in Common.Common.debug.js
I tried to use precompiled binaries of ACT : AjaxControlToolkit.Binary.NET35.zip and its working!
There is difference in referenced scripts between my dll and AjaxControlToolkit.Binary.NET35.zip
In my version, the headers of MicrosoftAjax.debug.js and MicrosoftAjaxWebForms.debug.js are:
// Name: MicrosoftAjax.debug.js
// Assembly: System.Web.Extensions
// Version: 3.5.0.0
// FileVersion: 3.5.30729.4926
//-----------------------------------------------------------------------
// Copyright (C) Microsoft Corporation. All rights reserved.
//-----------------------------------------------------------------------
// MicrosoftAjax.js
// Microsoft AJAX Framework.
// Name: MicrosoftAjaxWebForms.debug.js
// Assembly: System.Web.Extensions
// Version: 3.5.0.0
// FileVersion: 3.5.30729.4926
//-----------------------------------------------------------------------
// Copyright (C) Microsoft Corporation. All rights reserved.
//-----------------------------------------------------------------------
// MicrosoftAjaxWebForms.js
// Microsoft AJAX ASP.NET WebForms Framework.
And when im using version from AjaxControlToolkit.Binary.NET35.zip, they are:
// Name: MicrosoftAjax.debug.js
// Assembly: AjaxControlToolkit
// Version: 3.5.40412.0
// FileVersion: 3.5.40412.2
// (c) 2010 CodePlex Foundation
// Name: MicrosoftAjaxWebForms.debug.js
// Assembly: AjaxControlToolkit
// Version: 3.5.40412.0
// FileVersion: 3.5.40412.2
// (c) 2010 CodePlex Foundation
I have not compared the rest of scripts, but in those 2 scripts: assembly, version and author does not match between my and precompiled dll. ToolkitScriptManager is trying to load microsoft scripts, but it should load those from CodePlex.In solution downloaded from AjaxControlToolkit.Source.zip, there are 2 projects: MicrosoftAjax and MicrosoftAjax.Extened, i think ToolkitScriptManager should take scripts from them. Maybe im compiling it in a wrong way? (I changed target framework in AjaxControlToolkit project to .NET 3.5 and also tried to change it in 2 projects mentioned above, with no effect).
View 5 Replies
Apr 26, 2010
When adding the latest ajax control toolkit.dll to my VS environment, it throws a "AjaxControlToolkit.dll is not a Microsoft .Net module.
View 4 Replies
May 26, 2010
with build 30512 i was using client scripts including the .js this way:
<AjaxControlToolkit:ToolkitScriptManager ID="ScriptManager1" runat="server">
<Scripts>
<asp:ScriptReference Name="AjaxControlToolkit.Common.Common.js" Assembly="AjaxControlToolkit" />
<asp:ScriptReference Name="AjaxControlToolkit.Compat.Timer.Timer.js" Assembly="AjaxControlToolkit" />
<asp:ScriptReference Name="AjaxControlToolkit.Animation.Animations.js" Assembly=" AjaxControlToolkit" />
</Scripts>
</AjaxControlToolkit:ToolkitScriptManager>
now i receive this error (sorry, it is in italian) :
L'assembly 'AjaxControlToolkit, Version=3.5.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' non contiene una risorsa Web con nome 'AjaxControlToolkit.Common.Common.js'. Descrizione: Eccezione non gestita durante l'esecuzione della richiesta Web corrente. Per ulteriori informazioni sull'errore e sul suo punto di origine nel codice, vedere l'analisi dello stack. Dettagli eccezione: System.InvalidOperationException: L'assembly 'AjaxControlToolkit, Version=3.5.40412.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' non contiene una risorsa Web con nome 'AjaxControlToolkit.Common.Common.js'.
I am currently using some $common functions, like getContentSize() and so on.
Looking at the source code it seems to me that all the paths have been changed, but i cannot understand the right namespace to use with the latest release.
View 8 Replies
Feb 2, 2010
recently I start using AjaxControlToolkit 3.0.31106.0 and now i suddenly get an errors saying "Sys._ScriptLoader is undefined". Does the Sys._ScriptLoader not exist anymore and if so what is the alternative.
View 3 Replies
Feb 22, 2010
I'm trying to use the AsyncFileUpload control from the Asp.net Ajax Control Toolkit (Sept 30, 2009 stable build: 30930) . I've created a demo application and the control works fine. Files upload and all is well. When I try to use the control in my real application, I'm always receiving an error stating "The file attached is invalid". The AsyncFileUpload control returns this when the file uploaded is null.
To isolate the problem, I created a new master page exactly like the master page in my demo app. I also created an aspx page exactly like the page in my demo app. The upload still fails with a "The file attached is invalid" error. I also compared the web.config for the real app and the demo app and couldn't identify any differences that should matter. The code below is the test code in my real app. This code is exactly the same as the functioning code in the demo app with the exception of having different class names and file names. The web.config listed below is from the real app with the appsettings and connectionstrings removed. Real App Test Master Page:
<%@ Master Language="C#" AutoEventWireup="true" CodeFile="aaaMasterPage.master.cs" Inherits="L1Admin.aaaMasterPage" %>
<!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>
<script type="text/javascript" src="js/jquery-1.3.2.min.js"></script>
<asp:ContentPlaceHolder id="head" runat="server">
</asp:ContentPlaceHolder>
</head>
<body>
<form id="form1" runat="server">
<asp:ScriptManager ID="scriptManager" EnablePartialRendering="true" runat="server" AsyncPostBackTimeout="180" />
<div>
<asp:ContentPlaceHolder id="content" runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
</html>
Test Page:
<%@ Page Language="C#" MasterPageFile="~/aaaMasterPage.master" AutoEventWireup="true" CodeFile="aaaFileUploadTest2.aspx.cs" Inherits="aaaFileUploadTest2" Title="Untitled Page" %>
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="ajax" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<script type="text/javascript">
function pageLoad(sender, args) {
}
function startUpload(sender,args)
{
$('#uploadMessage p').html();
$('#uploadMessage').hide();
}
function uploadComplete(sender,args)
{
showUploadMessage(args.get_fileName() + " uploaded succesfully - " + + args.get_length() + " bytes", '');
}
function uploadError(sender, args)
{
showUploadMessage("An error occurred during uploading. " + args.get_errorMessage(), '#ff0000');
}
function showUploadMessage(text, color)
{
$('#uploadMessage p').html(text).css('color', color);
$('#uploadMessage').show();
}
</script>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="content" Runat="Server">
<div id="uploadMessage"><p></p></div>
<ajax:AsyncFileUpload ID="pageBannerUpload"
CssClass="file_upload"
OnClientUploadError="uploadError"
OnClientUploadStarted="startUpload"
OnClientUploadComplete="uploadComplete"
onuploadedcomplete="upload_UploadedComplete"
runat="server" />
</asp:Content>
Real App Test Page Code Behind:
using System;
using System.IO;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
public partial class aaaFileUploadTest2 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void upload_UploadedComplete(object sender, AjaxControlToolkit.AsyncFileUploadEventArgs e)
{
if (pageBannerUpload.HasFile)
{
string path = MapPath("~/") + Path.GetFileName(e.filename);
pageBannerUpload.SaveAs(path);
}
}
}
Real App Test Web.config:
<?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
WindowsMicrosoft.NetFrameworkv2.xConfig
-->
<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>
</appSettings>
<connectionStrings>
</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="true">
<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.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
</assemblies>
<codeSubDirectories>
<add directoryName="CSCode"/>
<add directoryName="VBCode"/>
</codeSubDirectories>
</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"/>
<add tagPrefix="Annsa" namespace="Annsa.Controls" assembly="Annsa.Controls"/>
</controls>
<namespaces>
<add namespace="Microsoft.VisualBasic"/>
<add namespace="System.Data"/>
<add namespace="System.Drawing"/>
</namespaces>
</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" validate="false" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
<identity impersonate="true"/>
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
<!-- SESSION STATE SETTINGS
mode="Off|InProc|StateServer|SqlServer"
By default ASP.NET uses cookies to identify which requests belong to a particular session.
If cookies are not available, a session can be tracked by adding a session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
-->
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20"/>
<!-- GLOBALIZATION
This section sets the globalization settings of the application.
-->
<xhtmlConformance mode="Legacy"/>
</system.web>
<location path="Pages">
<system.web>
<xhtmlConformance mode="Transitional"></xhtmlConformance>
</system.web>
</location>
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="OptionInfer" value="true"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
</compilers>
</system.codedom>
<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" verb="GET,HEAD" path="ScriptResource.axd" preCondition="integratedMode" 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>
View 3 Replies
Mar 3, 2010
I am using AjaxControlToolkit.dll 1.0.20229. For compiling my code in my DotnetNuke module. When I compile our code and upload it on Server Dotnetnuke application which is having latest 3.x version of AjaxControlToolkit.dll. I get following error. I am not compiling my code to a specific version of AjaxControlToolkit.dll.......................
View 2 Replies
Mar 28, 2011
I regularly run into the following error in my .NET 4.0 web application:
[Code]....
I found that the issue was already reported here: [URL], but there is no solution provided anywhere (at least, I didn't find it).
View 6 Replies
