AJAX Beta 1-Shame

I’ve been pushing Atlas at work to my boss, and even wrote portal just to show how cool it was. Well , I'm not sure what to do after this beta 1 release. It seems MS has changed rules during the game. PageMethods don't work. Controlstoolkit is... I even don't what to look into... I don't know. I should have been smarter and kept quiet about Atlas.

Shame on you Atlas team.

It's 4:00 AM and I’m going to bed. Tomorrow I’ll say sorry to my boss and move my app to SAP.

What a waste of time.

-A

Shame on you Atlas team? Are you familiar with acronyms? Are you familiar with Microsoft's CTP acronym? It stands for Community Technology Preview. You were implementing a CTP techology when you were implementing Atlas into your system. The risk you take with that is having to update your application with the changes once the technology has been improved (which it definitely has been in this case). Shame on you for pointing fingers at Microsoft's Atlas team when really you're the ONLY one to blame. Next time take five minutes of your precious time (I don't care if it is 4:00am) and search the forums for an answer to your problem because there was one posted before you submitted this infuriating trash.

- Chris

I’m all familiar with these words.

Also I familiar with words as: compatibility, and consistency, and before I wrote my post, I read other posts on this website and other blogs. Not one post offered solution toPageMethods problem, and if you search this forum,you’ll find many angry developers and not one will tell they liked what MS done with this beta.

If this framework was made available to us, with all this videos and tutorials (advertisement), at least MS should keep it consistent.

Yea, one more thing .

I’ve been pro (support) MS since day one.

I like almost every product they released, and I’ve worked with beta products too, but this been so far biggest disappointment for me.

For the rest of you, be very careful when you use this product in your projects at work. You might loose your job.

-A

I am as dissapointed as the rest with the changes from Atlas to the new Beta...

Why? I had to change my perception of thinking and the way I was providing a solution...

Guess what: When you deal with Beta - pre-release - you expect that and understand there are a team of developers that are working to provide 'solutions'. Granted they may not be what 'we expect' from what we 'are accustomed to' but BETA, Alpha, pre-release etc.. being an early adopter means that there is more to the community than just youself. One aspect I sympathise with the Asp.Net Team is that they deall with thousands of us - all wanting one thing or the other all for different reasons. Those of us trying to embrace new technology have to realize its BETA, ALPHA, CARLIE, ZEBRA or whatever.. until its a RTM - then what have you may...

The one thing about Scott Guthrie's Team is they ARE on the forefront. They didn't wait until MagicAjax, or other suddenly had marketshare... instead they have been almost rogue like in the Microsft enviroment in bucking the trends and reacting to developers needs... You can *** to no end about how pre betas change what the current Beta's entail-- however you would be hardpressed to excuse them as not trying. It is very hard on the business side to provide the best in features withou sacrificing other customers.. it a given... but in actual true fashion - they provide documentation.. examples.. blog posts from real experts... and do actually respond to and devlope against customer feedback. We may not see it al the time and most of us do not have the ability to pop up a laptop in each of their office to demonstrate a problem... Look at the bigger pictiure... constructive critism is great... tell al of us (the devs using the techonology and those at MSFT programming it) what your issues are.. but slamming for the mere aspect that code from July qand the Beta release breaks... gimme me a break... Its great to have opinions but unless you desire to part of the solution - we all are part of the

problem... I find great resentment in your post merely becuase its so - uggh single minded...You took the same risks as we all did and each of us has the ability to influence the outcome in a POSITIVE MANNER...Try to get this level of product support for something BETA from IBM , Oracle or the likes...

They listen - and due to volume may not be able to respond to all of us (and believe me I which they would to my concerns)but none the less this is a 'community forum'...

Lets just say we ecided to take whatever pill we decided.. but until somthing is actually released as 'productiion' ready... its all BETA and the only thing we can do is positively outline what our needs and concerns are...

hello

kdpo:

I’ve been pushing Atlas at work to my boss, and even wrote portal just to show how cool it was. Well , I'm not sure what to do after this beta 1 release. It seems MS has changed rules during the game. PageMethods don't work. Controlstoolkit is... I even don't what to look into... I don't know. I should have been smarter and kept quiet about Atlas.

Shame on you Atlas team.

It's 4:00 AM and I’m going to bed. Tomorrow I’ll say sorry to my boss and move my app to SAP.

What a waste of time.

-A

yes, it's true: there are no more page methods, at least instance ones. I've already spend half a day trying to explain why we are better off without them, but it still seems like there are lots of guys using it. I must say that i never thought that so many people were using instance page methods...and, as I already saidhere, I don't really think there's any justification for using them since the penalty you pay is to high and I still haven't found any good justification for using those methods.

make no mistake about it: in the previous i'm saying that instance page methods should be back because it seems like there are lots of guys which depend on it. To me, this dependency still means lack of knowlegder in javascript or will to write some javascript code and use a web method or a static method to do the same work.

I mean, most guys just forget that AJAX means writing javascript and went straight away to page methods without even thinking in the consequences of those actions...

The real "shames" of the new pagemethod are:

- Lack of support of the old method, both would be nice. (However the new one is better for me...)

- The annoying codebehind bug.

Check the descriptionhere, it's missing from the whitepaper.

hello.

i know that...and as i said, maybe there's space for both. in my opinion, no serious ajax page should use the old instance page methods...

Have to say I agree with others on this thread who are making the point that this isPre-Release software.

By all means look at it to get afeelfor where Microsoftmight be going with AJAX but I certainly wouldn't stake my job on it until it's gone RTM.

I for one think that the community involvement in this project is very valuable and worthwhile and will result in a much better end product than if MS had worked on this behind closed doors and only released it when it went RTM.

Migrating my app from July CTP to the new beta is requiring a lot of work, I assume it since it is prerelease software. But in my opinion, the really bad thing is: the beta has more bugs than the July CTP. I expected much more quality from this beta. I wonder why the ajax team guys have named it beta, I think they should just called it CTP.

Betaused to mean that a product was not to be used in production and was only being tested. Nowadays the rules have changed as Betas are made public and are in production. For example, Gmail is still marked as Beta but everyone uses it and it works pretty well. There are many examples of beta products being in production. The effect of this, unfortunately, is that the term beta has lost its meaning.

Because MSFT encourages developers to adopt pre-release products - it gives them some responsibility to make the products somewhat stable. My frustration is not the changes in the product but the bugs. Its not really usable.

Jesús:

Migrating my app from July CTP to the new beta is requiring a lot of work, I assume it since it is prerelease software. But in my opinion, the really bad thing is: the beta has more bugs than the July CTP. I expected much more quality from this beta. I wonder why the ajax team guys have named it beta, I think they should just called it CTP.

are you sure about this? i think this is not correct, specially if you concentrate on the core bits...

i think the main problem people are facing is that this beta is a complete new product which reuses several ideas of the ctp. so, it's as if we had to learn everything from the begining again. however, it's not fair to say that this release is worst that the previous one.

rsalit:

Because MSFT encourages developers to adopt pre-release products - it gives them some responsibility to make the products somewhat stable. My frustration is not the changes in the product but the bugs. Its not really usable.

hello.

i'm sure there are bugs, but it would help us all if we got a list (lke the one garbin developed) where everyone could put the bugs. btw, i've already seen 2 posts saying that this release has more bugs, but i see no one giving info on thebugs and on how to reproduce them.

[quote user="Luis Abreu] i'm sure there are bugs, but it would help us all if we got a list (lke the one garbin developed) where everyone could put the bugs. btw, i've already seen 2 posts saying that this release has more bugs, but i see no one giving info on thebugs and on how to reproduce them.
[/quote user="Luid Abreu]

bug description, repro, wokaround, and fix:

http://forums.asp.net/thread/1437484.aspx

[quote="Luis Abreu"] but i see no one giving info on thebugs and on how to reproduce them. [/quote="Luis Abreu"]

Bug description, repro and workaround:

http://forums.asp.net/thread/1440876.aspx

ajax beta 1.0 run well in firefox 2.0 , but does not work in IE6 SP1 (winXp or win2000)

I migrate my company website form atlas to ajax beta 1.0 ,but there are script erros in IE6 SP1 (winXP or win2000) when I call web serviece from javascript.the

win2000 OS is updated to SP4 and the winXP OS is updated to SP1,but ajax does not run. when some winXP pc OS is updated to SP2,ajax run well.

By compared, ajax run well in firefox 2.0.

there are many IE users who need my help to run my website ,but who can help me?

Hi,

ASP.NET team member, Chris Riccio has pointed that this problem maybe be caused by a bug in IE 6 SP1 concerning to HTTP compression. In fact, I was able to fix it installing the patch KB912812 on the clients.

AJAX Beta 1 error

Hello,

I just downloaded AJAX Beta 1, I have not used any of the previous Atlas version and this is my first stab at Microsoft's AJAX, on my dev machine and on the production machine I consistently get this same error message when a postback should occur from a dropdownlist:

"Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed"

I have search high and low on these forums and I can't seem to find a resolution to this. Here is the code on my aspx page that shows the scriptmanager and updatepanel:

<asp:ScriptManager id="scmAddItem" runat="server" EnablePartialRendering="True" />
<asp:UpdatePanel id="pnlCategory" runat="server" UpdateMode="Conditional" RenderMode="Inline">
<ContentTemplate>
Item Base Category : <asp:DropDownList ID="cmbItemCategory" AutoPostBack="true" OnSelectedIndexChanged="cmbItemCategory_IndexChanged" runat="server"></asp:DropDownList><br />
Choose Sub Category <asp:DropDownList ID="cmbSubCategory" runat="server"></asp:DropDownList>
</ContentTemplate>
</asp:UpdatePanel>

As you can see, I have one dropdown, that when changed should fire the OnSelectedIndexChanged event, but this doesnt seem to happen, I just consistently get the above error message. I copied the sample web.config and placed the dll's in the bin folder with no results.

Anyone come across this before? Any help would be greatly appreciated.

Thanks

Sean

This weekend many people have problems with ASP.NET 2.0 AJAX, thanks Scott Guthrie for releasing something on Friday!

Do you have the problem in every page or just one? Because looks like the project is not set up properly. Got a post about setting up the Atlas projects, however I need to see if still applies to the new ASP.NET 2.0 AJAX (name to long)

http://alpascual.com/blog/al/archive/2006/07/12/Setting-up-Atlas-to-existing-Web-Projects-without-using-the-template-_2800_-Visual-Studio-2005-_2900_-.aspx

Please, let me know if that helps you, if not, I'll update the article with a new set up for ASP.NET 2.0 AJAX ( What about just calling it Atlas?)

Ok,

This is what I have found out so far, If I create a new page, and put my updatepanel in it, it updates properly as expected.

It seems to only be a problem with this one page in peticular where I have a series of complex steps setup, I was trying to add ajax functionality to it and I can't seem to get around the error message I am receiving, i am thinking perhaps it is something with ViewState?

I am doing some more testing now, and I will report back when I find the cause.

Quite strange.

I dont know if it is right solution. I had same problem. If you look at your rendered page so there is in JS method forexample

Sys.WebForms.PageRequestManager.getInstance()._updateControls(['tctl00$cphCenter$UpdatePanel1'], [], [], 90); , but no tctl00$cphCenter$UpdatePanel1 object isn't on page. So when i am rendering the page i replace tctl00$cphCenter$UpdatePanel1 with right id ctl00$cphCenter$UpdatePanel1 without t at the begining and there is no error no more.

Hope this helps. If not so sorry. 

Well it seems that that T is there rightly. I have read MicrosoftAjaxWebForms.js and found it but for the moment i don't understand it. So sorry

AJAX Beta 1 and PageMethods Error

Hello,
I'm using the PageMethods to call page methods. All works with the ATLAS CTP.
With the new AJAX Beta 1 I have an error: PageMethods is undefined. I don't think it's a problem of my web.config. If i create a new ASP.NET AJAX Enabled Web Site I have the same error.

Someone have the same error? Is it a bug? Is it a beta 1 change?

Thanks,
Alessadro

hello.

make sure that your page method is public and STATIC (this is a change from the previous ctp version). btw, make sure that the method receives all the values that it needs to perform its calculations since now you don't get access to the controls maintained on the page.

I have checked all this things before posting.
My methods are public and static and have the attributes Microsoft.Web.Script.Services.ScriptMethod and WebMethod.
They use only local variables and don't access any page controls.

I think that the error is different: PageMethods is undefined. I have this javascript error, so I don't think it's a problem with my methods. It's the PageMethods that is not defined.
If i define a simple method that return an integer, I have the same error. And I have the same error if i create a new ASP.NET AJAX Enabled web site project too.

hello again.

if i recall correctly, you just need to use the webmethod. here's a quick example i have here:

<%@. Page Language="C#" %>
<%@. Import namespace="LivroAtlas"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script runat="server">
[System.Web.Services.WebMethod]
public static Aluno[] ObtemAlunos()
{
Aluno[] alunos = new Aluno[]{
new Aluno( "João", 15 ),
new Aluno( "Rita", 16 ),
};

return alunos;
}
</script>
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<asp:ScriptManager runat="server" ID="manager" />
<input type="button" value="invocar método da página" onclick="handle()" />
</form>
<script type="text/javascript">
function handle()
{
PageMethods.ObtemAlunos( handleCallback);
}
function handleCallback( res )
{
for( var i = 0; i < res.length; i++ )
{
alert( res[i].Nome + "-" + res[i].Idade );
}
}
</script>
</body>
</html>

btw, if you check the source of your page and don't see the global variable PageMethods, then that means that the ScriptManager is not injecting the proxy for the methods on the client side...

Finally I resolved the problem.
The solution is describe in this post from Shawn Burke's Blog. Due to a bug in this release of AJAX the page method must be in the same ASPX Page and not in codebehind.

Did you do anything to get the PageMethods object to appear on your page?

I've got public static void, I've got WebMethod and ScriptMethod, and I've got the function in the page rather than the code-behind... still nothing.

what the.......

okay... apparently closing the project, leaving it overnight, and changing absolutely nothing... fixed it... what do ya know. :p

This will break too much of my code...I think I will revert back to ATLAS until this is resolved/changed.

AJAX Beginner HELP!!

I checked out the instructional videos provided on this site for the Microsoft AJAX but it is all for the ATLAS release.

Take for example here is some of the code that I have from one of the videos

<%

@dotnet.itags.org.PageLanguage="VB"AutoEventWireup="false"CodeFile="Default.aspx.vb"Inherits="_Default" %>

<%

@dotnet.itags.org.RegisterAssembly="Microsoft.Web.Atlas"Namespace="Microsoft.Web.UI"TagPrefix="atlas" %>

<%

@dotnet.itags.org.RegisterAssembly="AtlasControlToolkit"Namespace="AtlasControlToolkit"TagPrefix="atlastoolkit" %>

<!

DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<

htmlxmlns="http://www.w3.org/1999/xhtml">

<

headrunat="server">

<

atlas:ScriptManagerID="PageScriptManager"runat="server"EnablePartialRendering="True"/>

<

atlastoolkit:HoverMenuExtenderID="HoverMenuExtender1"runat="server"><atlastoolkit:HoverMenuPropertiesTargetControlID="btnProduct"PopupControlID="PanelPopUp"PopupPosition="Left"PopDelay="25"/></atlastoolkit:HoverMenuExtender>

<

title>Untitled Page</title>

<

styletype="text/css">

/*Hover Menu*/

.popupMenu

{position:absolute;visibility:hidden;background-image:url(images/header.png);opacity:.9;filter:alpha(opacity=90);

}

.popupHover

{background-image:url(images/header-opened.png);background-repeat:repeat-x;background-position:lefttop;background-color:#F5F7F8;

}

</

style>

</

head>

<

bodystyle="text-align: left"><formid="form1"runat="server"><br/><table><tr><tdstyle="width: 80px"><asp:PanelID="PanelPopUp"runat="server"Width="80"BackColor="white"CssClass="popupMenu"><asp:LinkButtonID="BtnUpdate"runat="server"CausesValidation="True"CommandName="Update"Text="Update"></asp:LinkButton> <br/><asp:LinkButtonID="BtnDelete"runat="server"CausesValidation="False"CommandName="Cancel"Text="Delete"></asp:LinkButton> </asp:Panel></td><tdstyle="width: 100px"><asp:LinkButtonID="btnProduct"runat="server"Width="273px">Product Number One</asp:LinkButton></td></tr></table></form>

</

body>

</

html>

Now the big issue is I just installed the new Beta 2 I do not have the ATLAS installed. I do not get any options for AJAX controls or code and I created a new website using the option for "ASP.NET AJAX-Enabled Web Site"

Please tell me what is going wrong do I need to uninstall and reinstall everything.

Also I am using the Visual Studio Express Web

Thank you for any help you can provide on this

hello.

1st, the ajax extensions have changed the prefix name used...there's a breaking change document which explains this on the ajax.asp.net site

you should also note that you need to download the toolkit pack from codeplex in order to use it...

AJAX and the Querystring

Having a slight problem with Atlas/Ajax. I have an item page which displays items based on the item id being passed by querystring into the page. The querystring parm is useful for bookmarking the exact product to be displayed on the page and returning to it later. If people click on a "go to next item in item category" button on this page, they get the next item in the category displayed and the URL querystring item parm changes to that item number. I accomplish this with a Response.Redirect to the same page with the new querystring parm value, but I can't seem to do this with an Ajax setup because the redirect loads the page over again.

How do I keep the benefits of Ajax by having a client side refresh without reloading the page and alter the querystring to the new product number?

what u store in the query string could also be stored in the session object & the session object could be passed as a parameter to the database.

That's a good suggestion; but the issue would be the user coming back to the page at a later point, having changed the item id on the querystring via the show next item in category button. They may wander off; close their browser; destroying the session info and then want to return to their "bookmarked" page. Even if I kept the data in the DB for retrieval and could identify that customer coming in again, how would I know which product they were after? What if they bookmarked two different products originally. I wouldn't have the querystring information under AJAX to know that. I don't think I would want to show them "last product viewed" when they come back in.

write a small procedure to evaluate the query string when the user comes back.if there is a query string, pass that to the session & databind.so in any case, whether there is a session variable or not you would be able to databind.

hello.

well, i think that's not he problem he wants to solve. what he needs to do is to change the query string so that it identifies the current product but he doesn't want to perform a navigation when changing the query string.

hum...i really don't know if you'll be able to do that...try to look at the location object, though i really think this is only ie specific

Luis,

I think you described exactly what I want to do. I can do it server side with no issue using a redirect, but client side with AJAX is a problem, even though AJAX does a great job with client side refreshes on the page!

hello.

well, the problem is that what you're trying to do is not an ajax related thing. i mean, for the browser, the query string really isn't something that you can program against. it's just an url, so i think that changing it for adding or modifying a query string parameter will force the browser to navigate to a new url. if this is not a problem to you, then simply changing thw window.location property will do what you want from the client side. however, you should note that this is the same as loading a new page in the browser...

ajax and login

when i try to put login inside updatepanel get error message

in old version (atlas) login work cool if u enabledauthenticationService in web.config

<authenticationServiceenabled="true" />

any one can help please

hello.
are you talking about the asp login control? If so, i think it doesn't depend on the <authenticationService>?element...

AJAX and Atlas

I've noticed that atlas.asp.net has been changed to ajax.asp.net. First, does anyone know the difference between the two and second, which is the better choice to move forward with?http://weblogs.asp.net/scottgu/archive/2006/10/20/ASP.NET-AJAX-Beta-1-Released.aspx