Did I miss something during installation of AJAX 1.0v?

Hi everyone;

I'm using VS2005 and I've just installed AJAX and it works but in the source view it underlines Script Manager, UpdatePanel, contenttemplate and controls under contenttemplate. I guess I missed something that I don't know:) My simple page code is belove:

Thanks... Kaan ?ZGEN

<%

@dotnet.itags.org.PageLanguage="VB"MasterPageFile="~/Copy of Turuncu.master"AutoEventWireup="false"CodeFile="DNM2.aspx.vb"Inherits="DNM2"title="Untitled Page" %>

<%

@dotnet.itags.org.RegisterSrc="Menu.ascx"TagName="Menu"TagPrefix="uc1" %>

<

asp:ContentID="Content1"ContentPlaceHolderID="ContentPlaceHolder1"Runat="Server"><asp:ScriptManagerid="ScriptManager1"runat="server"/>

<asp:UpdatePanelid="UpdatePanel1"runat="server"UpdateMode="Conditional"><contenttemplate><asp:Labelid="Label1"runat="server"Text="Label"></asp:Label><asp:Buttonid="Button1"runat="server"Text="Button"></asp:Button></contenttemplate></asp:UpdatePanel> <asp:LabelID="Label2"runat="server"Text="Label"></asp:Label><asp:LoginID="Login1"runat="server"></asp:Login><uc1:MenuID="Menu1"runat="server"/>

</

asp:Content>Have you installed SP1 for VS 2005? That can happen if you haven't.

Is there such service pack?? Thanks I didn't know it... :) I'll try and let you know if solved..

Kaan ?ZGEN

Hi mdenn;

Yes that was the problem; now because of you (sayende) I got SP1 and my problem is solved

Thanks..

Kaan ?ZGEN

Deploying Atlas to Non Dev Machines

I have an intranent application that gets iframecall.axh errors when deployed. It if I change the script manager paths to point back to a development box.(?).

Debug error message: "A web request made using the iframe executor failed. Make sure that the app's web.config registers iframecall.axd"

What am I missing? Something must need to be done to these test machines to deploy.

The http handler is set :

<addverb="*"path="iframecall.axd"type="Microsoft.Web.Services.IFrameHandler"validate="false"/>

Each of the Web Methods.

WebOperationAttribute(true,ResponseFormatMode.Json,true)

Why does Atlas use the header name and the port to call its self? I found the cause of the problem. Its appears that since we use a CSS ( type of cysco router ) to route traffic on shared servers that the call to the service is using the host header and the port which when re-routed back to the server is incorrect. If the site is available on http://<server>:<port> but the users calls it with the host

headerhttp://<host header> the call back to iframecall ishttp://<host header>:<port>

Here is an example: http://MySite/service1.asmx if hosted onhttp://MyServer:8040/service1.asmx gets called viahttp://MySite:8040/service1.asmx and fails.

Is there a work around for this or how do I fix it?