Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts

Wednesday, March 28, 2012

AJAX Breaks the asp:Treeview

It is also a generally unstable browsing and development experience, but there's enough posts on that already.

I have the .Net AJAX RC installed. Create a simple AXAJ enabled web site, add a Label to display the selected node values, and a treeview using an xmldatasource. The XML has to be somewhat deeply nested to get the bug, about 6 levels deep. Wrap it all in an update panel and watch it explode when you try to navigate the tree.

protected void TreeView1_SelectedNodeChanged(object sender, EventArgs e)
{
this.TreeNodeValue.Text = TreeView1.SelectedNode.Value + "::" + TreeView1.SelectedNode.Text;
}

<body> <form id="form1" runat="server"> <asp:ScriptManager ID="ScriptManager1" runat="server" /> <asp:UpdatePanel ID="updTreeView" runat="server"> <ContentTemplate> <asp:Label ID="TreeNodeValue" runat="server" /> <div> <asp:XmlDataSource ID="dsTreeview" runat="Server" XPath="entity" DataFile="~/App_Data/ReportsTree.xml" /> <asp:TreeView ID="TreeView1" runat="Server" DataSourceID="dsTreeview" ExpandDepth="2" NodeIndent="8" OnSelectedNodeChanged="TreeView1_SelectedNodeChanged"> <RootNodeStyle CssClass="RootNode" /> <ParentNodeStyle CssClass="ParentNode" /> <LeafNodeStyle CssClass="LeafNode" /> <HoverNodeStyle CssClass="HoverNode" /> <SelectedNodeStyle CssClass="SelectedNode" /> <NodeStyle CssClass="Node" /> <DataBindings> <asp:TreeNodeBinding DataMember="entity" TextField="name" ValueField="SubjectID" PopulateOnDemand="true" ToolTipField="name" ImageToolTipField="ResourceType" /> </DataBindings> </asp:TreeView> </div> </ContentTemplate> </asp:UpdatePanel> </form></body>
 
 
<entity SubjectID="1" ResourceType="Company" ImageURL="images/ResourceIcons/Company.gif" name="Company"><entity SubjectID="2" ResourceType="Application" ImageURL="images/ResourceIcons/Application.gif" name="Impact Analysis"><entity SubjectID="3" ResourceType="Scope" ImageURL="images/ResourceIcons/assembly.gif" name="Horizon"><entity SubjectID="4" ResourceType="Namespace" ImageURL="images/ResourceIcons/namespace.gif" name="Bip.Horizon.Holding"><entity SubjectID="5" ResourceType="ClassList" ImageURL="images/ResourceIcons/Folder.gif" name="Classes"><entity SubjectID="6" ResourceType="Class" ImageURL="images/ResourceIcons/Class.gif" name="Bip.Horizon.Holding.Holding" Modifier="Public" ClassType="Class"><entity SubjectID="7" ResourceType="MethodList" ImageURL="images/ResourceIcons/Folder.gif" name="Methods"><entity SubjectID="8" ResourceType="Method" ImageURL="images/ResourceIcons/Method.gif" name=" 'BIP.Horizon.Holding.Holding.GetProfileMarketCapAllocations" Modifier="Public"><entity SubjectID="9" ResourceType="Return Type" ImageURL="images/ResourceIcons/Class.gif" name="Return Type" DataType="System.Data.DataTable"></entity><entity SubjectID="10" ResourceType="Argument List" ImageURL="images/ResourceIcons/Folder.gif" name="Arguments"><entity SubjectID="11" ResourceType="Argument" ImageURL="images/ResourceIcons/Column.gif" name="dsRebalanceAdjustedHoldingsByAccount" DataType="BIP.Horizon.Holding.RebalanceAdjustedHoldingsByAccountDS" type="BIP.Horizon.Holding.RebalanceAdjustedHoldingsByAccountDS" Modifier="ByRef"></entity><entity Modifier="ByRef" SubjectID="12" ResourceType="Argument" ImageURL="images/ResourceIcons/Column.gif" name="dsProductMarketCapRange" DataType="BIP.Core.Product.ProductMarketCapRangeDS" type="BIP.Horizon.Holding.RebalanceAdjustedHoldingsByAccountDS"></entity><entity Modifier="ByRef" SubjectID="13" ResourceType="Argument" ImageURL="images/ResourceIcons/Column.gif" name="intMarketCapRangeID" DataType="int" type="int"></entity></entity><entity SubjectID="14" ResourceType="Call List" ImageURL="images/ResourceIcons/Folder.gif" name="Callers"><entity SubjectID="15" ResourceType="Method" ImageURL="images/ResourceIcons/Method.gif" name="BIP.Horizon.Web.UI.Account.aspx.cs"></entity></entity><entity SubjectID="16" ResourceType="Callee List" ImageURL="images/ResourceIcons/Folder.gif" name="Callees"><entity SubjectID="17" ResourceType="Method" ImageURL="images/ResourceIcons/Method.gif" name="BIP.Horizon.Product.GetMarketCapRanges"></entity></entity><entity SubjectID="18" ResourceType="Data Object List" ImageURL="images/ResourceIcons/Folder.gif" name="Data Objects"><entity SubjectID="19" ResourceType="DataObject" ImageURL="images/ResourceIcons/Database.gif" name="spbip.Horizon.Product.GetMarketCapRanges"></entity></entity></entity></entity></entity></entity></entity></entity></entity></entity>

 
 

The treeview control is not supported in the updatepanel by the docs. I hope this will be change in the future or we'll get a new real ajax treeview. I am using the treeview in updatepanel since the first ctps. I have some problems with it (for example with EnableClientScript="true"), but with some hacks it works for me.

The main problem for me that the treeview+updatpanel could be very slow, because the treeview needs enableviewstate="true" to works properly.Sad

First I world try to turn off any extra on the treeview especially this:

PopulateOnDemand="true" ->PopulateOnDemand="false"
I didn't try your code by I suppose that populating the nodes on the client side then expanding/collapsing/selecting a node could be easilystay out of the sync with the viewstate/server side.That was my problem with EnableClientScript="true".


AJAX Beta 2 web.config

Is there any documentation describing the sections needed in the web.config file to implement asp.net ajax into a site? I have installed it and am using it happily but I want an explanation of each element that is in that web.config template and why it is required, what I dont know worries me!

Thanks!

This is an excellent question.

I am going to give an explaination off my head:

First off:DOCS.

<configSections>
<sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<sectionGroup name="scripting" type="Microsoft.Web.Configuration.ScriptingSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<sectionGroup name="webServices" type="Microsoft.Web.Configuration.ScriptingWebServicesSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<section name="jsonSerialization" type="Microsoft.Web.Configuration.ScriptingJsonSerializationSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" />
<section name="profileService" type="Microsoft.Web.Configuration.ScriptingProfileServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" />
<section name="authenticationService" type="Microsoft.Web.Configuration.ScriptingAuthenticationServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" />
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>

^^ This just defines how the config sections are laid out in the following markup in the config file.

The important stuff we should concentrate about is the inner section webServices and the sections below that (the outer ones just defines the layout of the config kinda (dumb sections that does nothing but define themselves ))

--

jsonSerialization,profileService,authenticationService are all on the same level. These actually have usable elements you can configure.

You should read the docs on what the classes are (they are vague though) but web.config found in C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025

has an actual section + comments:

<microsoft.web>
<scripting>
<webServices>
<!-- Uncomment this line to customize maxJsonLength and add a custom converter -->
<!--
<jsonSerialization maxJsonLength="500">
<converters>
<add name="ConvertMe" type="Acme.SubAcme.ConvertMeTypeConverter"/>
</converters>
</jsonSerialization>
-->
<!-- Uncomment this line to enable the authentication service. Include requireSSL="true" if appropriate. -->
<!--
<authenticationService enabled="true" requireSSL = "true|false"/>
--
<!-- Uncomment these lines to enable the profile service. To allow profile properties to be retrieved
and modified in Atlas applications, you need to add each property name to the setProperties and
getProperties attributes. -->
<!--
<profileService enabled="true"
readAccessProperties="propertyname1,propertyname2"
writeAccessProperties="propertyname1,propertyname2" />
-->
</webServices>
</scripting>
</microsoft.web>

jsonSerialization section can have defined custom converters, if you have an object that you want to provice your own notation for, do it here.

I don't know too much about the other stuff, but it seems pretty straight forward...

--

Moving on:

<pages>
<controls>
<add tagPrefix="asp" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagPrefix="asp" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</controls>
<tagMapping>
<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CompareValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CustomValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RangeValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RegularExpressionValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RequiredFieldValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="Microsoft.Web.UI.Compatibility.ValidationSummary, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</tagMapping>
</pages>

^^ <controls> will map the prefix 'asp' to the AJAX controls (mainly updatepanel, scriptmanager, updateprogress etc) GLOBALLY across the whole site, so you don't have to provide it in the directive on each page ( This is VERY useful to use on your own controls, this is a true blessing!)

The <tagmapping> will replace the stock ASP.NET validator controls with the ASP.NET AJAX ones. This is to override the original stock validator controls to make them work properly.

--

<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" validate="false"/>
</httpHandlers>

First one replaces all requests (post, get (etc?)) to asmx files to the ScriptHandlerFactory. This factory is undocumented, but I can tell that it switches between 2 handler factories (it wraps them on a condition)

First one of them is RestHandlerFactory (undocumented), this will get chosen if it is a rest (if pathinfo starts with "/js").

If not, it will choose the stockWebServiceHandlerFactory class.

ScriptResource,axd axd is AJAX' own handler for processing script resources. This seems to be well documented (compared to other ajax stuffStick out tongue).

--

<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<add name="ScriptModule" preCondition="integratedMode" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-ISAPI-2.0"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode"
type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="ScriptResource" verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" />
</handlers>
</system.webServer>


^^ This is the section for IIS 7.0 (or any web server that reads this section. maybe cassini?).

This will remove WebServiceHandlerFactory-ISAPI-2.0 and inject the script handlers / modules.

Some is documented, some is not. But this is probably to make the script stuff work, to use regular English. Big Smile

This is only from the top of my head. Some are facts, some are just my assumptions!

Anyway, hope it helps, and if it really is an answer to you,mark it as answer, thanks!


hello.

the final section will only be used by IIS 7 (and i do think that the web.config that comes with ajax beta 2 is not complete).

btw,?EmilChristopherMelar is there any contest with cool prizes or something like that? why are you asking for your answer to be marked at the end ofyour posts?
Because then you can see that a thread is really answered, so people can see that it doesn't need any more attention, duh.
hello.

well, didn't really know that there are people on this forum trying to find threads that need attention...

It's not about that. It's about aknowledging the answer so I don't have to follow it up anymore.

It is common sense and usage of news / forums to give a response on a successful / unsuccessful answer.

And what's the point of answering if it's not read / acknowledged? What would the motivation for helping be if your answer is blatantly ignored?

Monday, March 26, 2012

AJAX assembly version

Trying to figure out if one of our hosting services has MS AJAX installed in the GAC and what version (Beta 2?) it is. The response from tech support was:

"We are currently running AJAX assembly version 5.7.22.2"

This doesn't sound right, can anyone who has the assembly installed verify the version number? I'm still developing a site with Atlas so don't want to install it on localhost.

Thanks for any info on this.

Thank You,

Cody Mejia
Support Technician
CrystalTech Web Hosting Inc.
A Newtek Business Services Company
Toll Free: 1-877-323-4678? Opt. 2
Phone: (602) 263-0300 Opt.? 2
Fax: (602)263-0600
URL:?http://www.crystaltech.com????
?
?
**Both "CrystalTech Web Hosting" and "Newtek Business Services" are trademarks of Newtek Business Services, Inc.**

",1]);D(["mb","


From:support@dotnet.itags.org.crystaltech.com
Sent: Wed, 15 Nov 2006 12:27:38 -0700
To: <mla@dotnet.itags.org.itinko.com>
Subject: [169-0CEDBD55-9C80]ASP.NET AJAX",1]);//-->

The Beta 2 (Nov Release) is 1.0.61025.0 - I think that is a June CTP of Atlas the 5.x you stated..

AJAX Assembly

I am running visual studio on my desktop and laptop. Both have had the AJAX Control toolkit and AJAX extensions installed. I mostly do my development work on my desktop but every once in a while I take my laptop. When I take my laptop I copy and paste the visual studio 2005 folder from 'documents' and copy it onto my laptop.

I've just done this recently and I am getting errors "Unrecognized tax prefix or device filter 'ajaxToolkit' on all my ajax controls. When I create a new page and insert an ajax control Visual Studio registers an assembly 'Assembly="AjaxControlToolkit" and tags it as "cc1". On my desktop visual studio doesn't register any assembly. It just calls the control <ajaxToolkit:...> and things work.

I've checked the bin folder and it does contain the AJAX dll. I'm sure it's something simple here, can someone tell me what is missing? Thank you.

try this in your aspx

<%@.RegisterAssembly="AjaxControlToolkit"Namespace="AjaxControlToolkit"TagPrefix="cc1" %>


I know about registering the assembly this way. I was wondering why on my desktop machine I don't have to register the assembly in my aspx and when I open it on my laptop I, all of a sudden, do.


Hi,

This can be also registered in web.config.

For instance:

<system.web>
<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>

Ajax application not working when deployed to web server

I installed the extender and then the toolkit and was able to create the sample application described here:http://ajax.asp.net/ajaxtoolkit/Walkthrough/UsingSampleExtender.aspx

However, when I deploy the webpage to my company's web server I get the following error when I try to run it:

Server Error in '/ajaxtest' Application.

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (E:\WebSites\ajaxtest\web.config line 41)

Source Error:

Line 39: </httpHandlers>Line 40: <httpModules>Line 41: <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>Line 42: </httpModules>Line 43: </system.web>


Source File:E:\WebSites\ajaxtest\web.config Line:41


The file it is referencing (E:\WebSites\ajaxtest\web.config) is there. Does anyone have any idea what's going on? I've Googled the problem and searched on here but nothing seems to work.

Thanks in advance!

Do you have System.Web.Extensions.dll in the bin directory in the server?

Do you mean the bin application of my AJAX enabled web app?

If so, that particular DLL is not in the bin folder, but it's not in the bin folder on my local machine either and it runs fine there. It just doesn't run on the web server.


If you don't have a bin of your application in the bin folder, maybe it's because you don't have a webApp project but a web site project. But, in both cases, you should have more dll's in the bin folder and that dll's should be copied to the bin folder on the server!

That's true. It is a web site project and not a web app project. However, I do have a bin folder for the application on my development machine and the server. When run on my development machine the application works, but when run on the server it doesn't. And neither bin folder has the dll you mentioned.

I'm sorry if I was confusing before.

Regardless, I will see about getting that dll into the proper folder and see what happens from there. Thanks again for your help and advice!


The dll you need should be here:

C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\System.Web.Extensions.dll

Put it on bin folder on server and it should work, I hope. :P


SWEET! That did the trick!

Thanks a million, Agapito! I really appreciate it.


Gracias! Friend! it worked.

Yes

AJAX and WebDeveloper2005 - Getting errors

Hello!

I installed the BETA Version of WebDeveloper 2008 and later I installed the AJAX-Extension for ASP.NET 2.0, because my ISP only supports ASP.NET 2.0.


Ok, I've heard that there can be some problems with the System.Web.Extension dll and so I have run the script from http://weblogs.asp.net/scottgu/archive/2007/07/26/vs-2008-and-net-3-5-beta-2-released.aspx

Now I get an other error when trying to add a ScriptManager to a special page (I'm using again WebDeveloper2005):

A dialog pops up telling me that hecouldn't load the file or assembly "System.Web.Extension Version=3.5.0.0"...

What can I do? The thing is, that I don't want to use the version 3.5.0.0 but the version=1.0.61025.0

Thank you for any suggestions!

Vs 2008 RTM is out. Maybe you can try to uninstall the beta and install the 2008 rtm wd express. Check ScottGu's blog for how to uninstall the beta, and where to get the rtm.


Thanks for your reply!

But I need to use the ASP.NET 2.0 framework, and I don't see a possibility to do this in the new 2008 version of VWD. Well, I could manually edit the Web.Config file, but I believe that there must be a much easier way to do all this...

I just want to use AJAX in VWD with framework 2.0...


When you create a new web site there is an option to choose the target framework (2.0, 3.0, 3.5). 2.0 should work with asp.net ajax extension 1.0

I'm not sure about whether this option is available in express edition, I tried with a pro version.


Hm yes, I saw this option in a video I found here on asp.net, too But in VWD 2008 Express I do not see this option...


According to this video

Video: Introduction to Visual Web Developer 2008 Express Edition

we cannot choose target framework in the express edition.

You can now tryVisual Studio 2008 Professional Edition trial (last week there is only the team system trial). Unfortunately there is no "standard" trial yet.

There is a good feature comparison for vs 2005 (Product Feature Comparisons), unfortunatelly I cannot find (yet) similar for vs 2008.

Saturday, March 24, 2012

AJAX and Vista -

I just upgraded to Vista from XP where I had IIS running very happily and AJAX installed and working great.

After upgrading to Vista I get this browser error on any AJAX website:

'Sys' is undefined

I remember seeing that error months ago back when it was called Atlas. But now that I'm running the latest OS, with a non-beta AJAX, why should I be getting this now? The upgrade to Vista has been painful all around, but I've managed to fix or find workarounds for most problems except this one.

It seems like the AJAX stuff isn't getting included into the webpage. I even tried creating a fresh project in VWD and specifying to use the VS template for "ASP.Net Ajax Enabled Website" and throwing together a simple page with an updatepanel and a command button. Same error.

I've run Windows Update and gotten all the updates, including the Visual Studio update that tells you to run VWD "as an administrator", which I'm doing.

The line in the generated page that it is complaining about is the first reference to Sys below.
Hopefully there is just some simple security setting in this locked down OS I don't know about to allow this to run? 
<script type="text/javascript">//<![CDATA[Sys.WebForms.PageRequestManager._initialize('ScriptManager1', document.getElementById('form1'));Sys.WebForms.PageRequestManager.getInstance()._updateControls(['tUpdatePanel1'], [], [], 90);//]]>
</script>

Do you have following entry in your web.confg file?

<add verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" validate="false"/>

Also, follow Readme notes on migration issues on ajax.asp.net .


Yes, I have that. This was a functioning ASP.Net 2.0/AJAX 1.0 application when I had XP, but now that I'm running windows Vista, it doesn't work.

I did have to manually edit applicationHost.config in C:\windows\system32\inetsrv\config to add entries for ASP.Net 2.0 (it only had enties for 1.1), so I'm wondering if something must be added there to support AJAX.

I tried downloading and re-installing AJAX, rebooting, all the obvious stuff with no luck. Upgrading to Windows has ALMOST completely shut me down from developing.

I did just discover that when I use the VWD built in web server, AJAX works fine. So AJAX is "installed" correctly on my PC. But as far as when I use the full-blown IIS web server, AJAX is dead.

I didn't see anything in the README relating to Vista migration, only migration from previous versions of Ajax/Atlas, which is not what I'm doing.


Here is what I ended up doing as I spent nearly two days trying to rebuild my Dev machine after purchasing a Vista capable laptop.

1. Mark your site in IIS7 as an Application (The choice is there if you right click on virtual IIS7 entry in the expanded list under websites...

2. Make sure that you have included all of the IIS7 web.config entries:

<

system.web.extensions>

<

scripting>

<

webServices>

<!--

Uncomment this line to customize maxJsonLength and add a custom converter-->

<!--

<jsonSerialization maxJsonLength="500">

<converters>

<add name="ConvertMe" type="Acme.SubAcme.ConvertMeTypeConverter"/>

</converters>

</jsonSerialization>

-->

<!--

Uncomment this line to enable the authentication service. Include requireSSL="true" if appropriate.-->

<

authenticationServiceenabled="true"requireSSL="false" />

<!--

Uncomment these lines to enable the profile service. To allow profile properties to be retrieved

and modified in Atlas applications, you need to add each property name to the setProperties and

getProperties attributes.

-->

<!--

<profileService enabled="true"

setProperties="propertyname1,propertyname2"

getProperties="propertyname1,propertyname2" />

-->

</

webServices>

</

scripting>

</

system.web.extensions>

<

system.webServer>

<

validationvalidateIntegratedModeConfiguration="false"/>

<

modules>

<

addname="ScriptModule"preCondition="integratedMode"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

modules>

<

handlers>

<

removename="WebServiceHandlerFactory-Integrated"/>

<

addname="ScriptHandlerFactory"verb="*"path="*.asmx"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptHandlerFactoryAppServices"verb="*"path="*_AppService.axd"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptResource"preCondition="integratedMode"verb="GET,HEAD"path="ScriptResource.axd"type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

handlers>

</

system.webServer>

Note that the PipeLine extension for the configured site can be set for Integrated (default) instead of the Classic Mode.

With those two steps I was able to get a XP configured site migrated over with Ajax...


My web site is set up as an application, and it uses an application pool set up for ASP.net 2.0.

When I set that application pool to use to use the Integrated mode, I can no longer even load my website (gives 404 error).

This is crazy, this was a perfectly functioning website under XP, and "upgrading" to vista has broken it.

Is there anything in the applicationHost.config file that needs to reference AJAX? I'm at the end of my rope here, I'm about to just install XP and loose ALL my programs and setting just to get back to a usable machine!

AJAX and Toolkit

Last week I downloaded and installed AJAX and the associated toolkit viaASPAJAXExtSetup.msi andAjaxControlToolkit.zip respectively.

When I open thetoolkit.sln file in VS2005, I get a flock of error messages, most notable of which are messages to the effect that the app is unable to find the System.Web.Extensions.dll and System.Web.Extensions.Design.dll files.

In looking at the installed files I noticed the following differences between the AJAX Extensions files and the Toolkit Files:

o AJAX Extensions inC>Program Files>Microsoft ASP.Net>ASP.Net 2.0 AJAX Extensions>v1.0.61025 folder contains aweb.config file that includes numerous "microsoft.web" and "Microsoft.Web.Extensions" entries.

o AtlasControlToolkit files in C>Program Files>Microsoft ASP.Net, the resultant files also containweb.config files: One in each of the "SampleWebSite", "ToolkitTests", and "ToolkitWebsiteTemplate" sub-folders. Each of these threeweb.config files include numerous "system.web" and "System.Web.Extension" entries.

I assume that theSystem.Web.xxx is the appropriate syntax.

Is there possibly a newer version of theASPAJAXExtSetup.msifile that synchronizes the syntax between these two apps?

Is there something else that I may have missed?

(I had previously been using ATLAS: I uninstalled the ATLAS app, and deleted the toolkit folder before I installed teh AJAX apps)

Never mind.

I downloadedASPAJAXExtSetup.msi againand the toolbox now works OK.

All of the config files now match each other.

Wednesday, March 21, 2012

AJAX And Content Pages

Hi to all..

I have the binaries of ajax control toolkit i do not have installed ajax extensions. then how to use these features of ajax in my project - how to add reference of it?

I have designed a master page and all the other pages - that are content pages, so how to use AJAX control toolkit in content pages.

Hi there,

first of all you have to install the Ajax Extension package (MSI), then from your project, you have to add a reference to AjaxControlToolkit assembly. Finally, select the toolbox window, right click on there, add a new tab, for instance "Ajax Toolkit", and then right click on this new tab and select the "Choose Items" option, at this point a new window will be opened so then select the "Browse" button and click on the AjaxControlToolkit assembly and that's all. You will see the whole AjaxControlToolkit on your toolbox window.

I hope it helps.

Regards,

Fernando.



hi,,

thank you for give me suggession.

i have already done that thing but the problem is when i put <asp:ScriptManager>.. inside the content page the following build error comes there "unknown type <asp:scriptmanager>"

and second thing is

if it runs successfully then there is an error in web browser like in status bar of browser "done, But with errors..."

sys. - undefined.

these errors i've faces so far so please guild for that also..

Thank you

Bhavin