Problem converting from Atlas beta to Ajax

Hi,

I have an application that uses the Modal Popup Extender control. I developed it using the beta of Atlas, and now I'm trying to convert it to version 1.0 of Ajax.

I've removed the Atlas references and added the one for the AjaxControlToolkit. I replaced the Atlas ScriptManager tag with the new ASP:ScriptManger tag, and I replaced the Atlas ModalPopupExtender and ModalPopupProperties tags with the Ajax ModalPopupExtender tag. When I try to run the program, I get a Javascript error which says 'Sys' is undefined, and refers to the following code added at runtime:

Sys.Application.initialize();
Sys.Application.add_init(function() {
$create(AjaxControlToolkit.ModalPopupBehavior, {"CancelControlID":"rpPermitsPlus_ctl00_OkButton","DynamicServicePath":"/PP_ServiceWorkTicket.aspx","PopupControlID":"rpPermitsPlus_ctl00_pnlTennantStatus","id":"rpPermitsPlus_ctl00_mpeTennantStatus"}, null, null, $get("rpPermitsPlus_ctl00_btnReport"));

Can someone tell me what I've done wrong, and what I need to do to get this application working again? Thanks for your help!

You need to edit your web.config in multiple places as well. I would suggest you compare the sample web.config in the ASP AJAX with your own.
That did it. Thanks kp0!

Problem Deploying ASP .NET Atlas on Vista Beta 2.

Hi Everyone,

I have a problem installing the Atlas June CTP on Windows Vista Beta 2 (Build 5384). It always pops an error: "C:\Program Files\Microsoft ASP .NET\Atlas\v2.0.50727\VSISetup.InstallState is denied" and subsequently rolls back the installation.

Please help!!! :(

Hey All,

I forgot to add, the user under which I tried installing Atlas belongs to the Administrators group...

Thanx...

I am having the exact same problem, same version of Vista and user in adminstrators group.

Problem in Transporting from july ctp to beta 2

Hi!

I've been having a problem that i still can't resolve.

In July CTP i had this page that server.transfer to another page that had a bunch of custom made tab's. These tab's run by JavaScript and execute on each run a click in an hidden button, the hidden button made a request to fill the user control of that tab, during that request the UpdateProgress is runing.

Ok this worked in the July CTP release, but now in Beta 2 release it isn't working. It keeps giving an alert saying that server error 404 and server error 12030. Since error 404 is Page not Found exception i think it has to do with the non changing of the address bar address...

I've read some post's to try to see if i get some answer and everyone just keeps saying to use response.redirect. I don't want to use response.redirect, it makes 2 postbacks and i would have to throw the data that i need to transfer to that page by querystring and that is something that i can't have.

Can anyone give me some lights?

Thanks,

Sérgio

I forgot where I found this, but I found out that if you have any web methods you need to add:

[Microsoft.Web.Script.Services.

ScriptService()]

to the service.

Example:

///

<summary>

///

Summary description for wsSelectGroup_Data

///

</summary>

[

WebService(Namespace ="http://tempuri.org/")]

[

WebServiceBinding(ConformsTo =WsiProfiles.BasicProfile1_1)]

[Microsoft.Web.Script.Services.

ScriptService()]

public

classwsSelectGroup_Data : System.Web.Services.WebService

{

No WebMethods.

It's just a simple plain server side execute in a page that was reached through server.transfer

I just can't get why it isn't working anymore...

hello.

well, it looks like a specific case which is not widely used, can you build a demo site that reproduces the problem?

Hi,

I saw this thread and although my problem is not quite the same, I am too having difficulties when usingserver.transfer to load a page using an UpdatePanel, somehow navigating to an Ajax enabled page using server.transfer get the UpdatePanel mixed up with the path!

here is some demo code to illustrate my problem:

2 folders "folder1" and "folder2" containing respectivelly "callingPage.aspx" and "ajaxPage.aspx"

problem in using atlas

I just installed Atlas and in VS.NET 2005 beta 2, I get this error:

Error 1 Unrecognized attribute 'appliesTo'. Note that attribute names are case-sensitive. (C:\AtlasWebSite\web.config line 53)
It seems it doesn't want the appliesTo keyword on web.config. Any suggestion?

Depending on the version of ASP.net you have, you can simply remove the "appliesTo" keyword and then the web.config will work.
Also, make sure you download the appropriate VSI file from this page:http://beta.asp.net/default.aspx?tabindex=7&tabid=47
Choose the VSI you want (either the Blank Project one, or the Hands on Lab one), and from there you can choose either the RTM version, or the Beta 2 version.
Thanks,
Eilon

Eilon :

the link you posted goes nowhere..asked to login..??