I am using VS 2005 and have had no issues getting AJAX applications to work on my XP machine. I walked through much of the documentation and watched several of the videos. I have installed the ASPAJAXExtSetup.msi on my IIS server as prescribed and published my web project and deployed my web project to the IIS server. I'm running windows 2003 STD with updates. Needless to say it does not work. I mean no errors messages at all, and I get full round trips for my page instead of partial page refresh. I've deployed the absolute simplest of examples to. A page with a 2 labels and a button. 1 updatepanel with 1 label inside. Scriptmanager of course. Works fine on XP locally but not on server box. I do see some other posts and I have tried several suggestions. I have downloaded the AJAX extensions recently and I think most of the previous issues I see out there where resovled. The only item different is that I have VS 2005 installed on XP machine and not on Server. I would be hugely surprised though if I had to install VS2005 on all servers in my environment though. Web.config is basic and I will include:
<?xmlversion="1.0"?>
<configuration>
<configSections><sectionGroupname="system.web.extensions"type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<sectionGroupname="scripting"type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"><sectionname="scriptResourceHandler"type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"allowDefinition="MachineToApplication"/>
<sectionGroupname="webServices"type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"><sectionname="jsonSerialization"type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"allowDefinition="Everywhere" />
<sectionname="profileService"type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"allowDefinition="MachineToApplication" /><sectionname="authenticationService"type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"allowDefinition="MachineToApplication" />
</sectionGroup></sectionGroup>
</sectionGroup></configSections>
<system.web><pages>
<controls><addtagPrefix="asp"namespace="System.Web.UI"assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</controls></pages>
<compilationdebug="false"><assemblies>
<addassembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/></assemblies>
</compilation><httpHandlers>
<removeverb="*"path="*.asmx"/><addverb="*"path="*.asmx"validate="false"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<addverb="*"path="*_AppService.axd"validate="false"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/><addverb="GET,HEAD"path="ScriptResource.axd"type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"validate="false"/>
</httpHandlers><httpModules>
<addname="ScriptModule"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/></httpModules>
</system.web><system.web.extensions>
<scripting><webServices>
</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>
</configuration>
Ok, you didn't NEED to install the msi... all you really need to do is include the ajax (System.Web.Extentions.dll) in your bin folder
Now...
1) does the server have 2.0 installed?
2) is the server setup to allow Asp.Net pages? (by default they may be turned off)
3) is the site/folder/application setup to be using 2.0 and not 1.x?
1. Yes , server does have the .NET framework version 2.0 installed.
2. Yes, Asp.NET is allowed because simple example I placed out there does work in terms of pure ASPX stuff, but does not work in terms of AJAX functions. Other ASPX site work as well.
3. YES, 2.0
Interesting that I don't need to install full MSI. I will try your suggestion. I am actually wiping the box now and will start again will a clean install. Seems like it still should have worked though eventhough I installed the MSI. The install supposedly installs the Extentions DLLs
I'm working now.
Installing MSI apparently prevented my app from working correctly, but copying the DLL directly into bin directory worked fine.
No comments:
Post a Comment