ASP.NET AJAX Discussion and Suggestions

Re: Another Bug

albertpascual — Mon, 06 Nov 2006 22:06:16 GMT

I belive I know why you are getting this error.

If you look at the request params before you do your thing, you'll find id as a parameter in AJAX, so you were overriding that, change your param to another name.

Another Bug

manicsquirrel — Mon, 06 Nov 2006 19:51:40 GMT

I have an update panel on my page. Everything worked great until I added the following javascript function in script tags in the head:

function cmdPrint_Click(id){
var obj = window.open('print.aspx?form=driver&id=' + id,'Print','width=640,height=480');}

Afterwards, each time the update panel tried to post back I would receive the "Unknown Error" message box. However, if I replace the ampersand in "?form=driver&id" with "&" it works fine.

Re: Unofficial bug/issue list for the Atlas June CTP

Garbin — Tue, 08 Aug 2006 23:03:00 GMT

Hi,

repro for issue #25:

<%@ Page Language="C#" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<script runat="server">
    protected void Page_Load(object sender, EventArgs e)
    {
        if (Page.IsPostBack)
        {
            lblToUpdate.Text = DateTime.Now.ToString();
        }
    }
</script>

<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
    <title>Untitled Page</title>
</head>
<body>
    <form id="form1" runat="server">
    <atlas:ScriptManager id="scriptManager" runat="server" EnablePartialRendering="true"></atlas:ScriptManager>
    <div>
        <atlas:UpdatePanel ID="UpdatePanel1" runat="server">
            <Triggers>
                <atlas:ControlEventTrigger ControlID="RadioButtonList1" EventName="SelectedIndexChanged" />
            </Triggers>
            <ContentTemplate>
                <asp:Label ID="lblToUpdate" runat="server"></asp:Label>
            </ContentTemplate>
        </atlas:UpdatePanel>
        
        <asp:RadioButtonList ID="RadioButtonList1" runat="server" AutoPostBack="true">
            <asp:ListItem>Item1</asp:ListItem>
            <asp:ListItem>Item2</asp:ListItem>
            <asp:ListItem>Item3</asp:ListItem>
        </asp:RadioButtonList>
    </div>
    </form>
</body>
</html>

Re: Unofficial bug/issue list for the Atlas CTP

Luis Abreu — Thu, 03 Aug 2006 08:26:48 GMT

Howdy again.

well, i'm sorry, but i've lost hope in those feedback centers. you see, a few months ago when i started using ATLAS, i started posting the bugs on the feedback center. in most cases, i spent my time tracking the bug and writing code that would duplicate it and, within my limited knowledge, took the liberty of suggesting a fix for it.

at the time, the best answer i got was "Unable to reproduce the bug" which really sucks (to reproduce it you just need to run the sample i've posted - hey, most of them are still on the june ctp). so, i come to this forums and asked where to put the bugs. at the time, the answer was: put them here (in this forum) and we'll take care of them. well, again, i've copied the bugs and tried to document them the best i could.

unfortunately, it seems like the bugs are still here...not even Garbin's effort of putting everything on one place seems to have worked out...

well, so if you want the bugs on connect, then you'll have to enter them yousrself. I'm sorry, but i'm also a busy person and i'm not going to loose another hour to copy all the items i've found and that i've document on this forum (most of which have references on this post) so that when the next ctp is out they're still there. sorry, but no, i won't do that.

if you guys really want to solve the bugs, then this post already has way too many which exist for too long now!

Re: Unofficial bug/issue list for the Atlas CTP

kevindente — Wed, 02 Aug 2006 22:20:49 GMT

>Regarding status of bug, you can add/review bugs for Atlas at
> http://connect.microsoft.com.

Am I the only one for whom this is news? From what I can see, this has never been officially announced - a fact which has caused much frustration. Glad to see we finally have an official repository for bugs and suggestions.

Is there a specific category we should be using? .NET Framework? Web Development? Frameworks (I'm assuming that "Visual Studio and .NET Framework" is the Connection that we should be using - do let me know if that's wrong).

Re: Unofficial bug/issue list for the Atlas CTP

tholewis — Wed, 02 Aug 2006 18:43:55 GMT

The Go Live license allows you to put an application into a production environment for CTPs so that we can get real world feedback (which has been great).

Good point regarding the messaging and I have let the folks know.

Regarding status of bug, you can add/review bugs for Atlas at http://connect.microsoft.com. The good news about connect is that anything put in there goes directly into our issue tracking system.

Re: Unofficial bug/issue list for the Atlas June CTP

Knut Meltzer — Tue, 01 Aug 2006 08:05:20 GMT

Can you add this to your list?

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

BUG: Action bindings ignore direction

kevindente — Tue, 01 Aug 2006 02:59:50 GMT

Action bindings ignore the direction property - they always perform both in and out binding. Looking at the definition of Action.execute, it's apparent that it calls both evaluateIn and evaluateOut on each action binding, regardless of what directoin the binding is defined as.

Re: Unofficial bug/issue list for the Atlas CTP

Luis Abreu — Mon, 31 Jul 2006 20:01:44 GMT

tholewis:
The reason you are seeing bugs is that Atlas has not been released. It is still a community technology preview that allows folks to use Atlas and provide feedback to the product team.

what about the go live license? i don't have any atlas product out yet and if you ask me, i'll probably say that currently i'll only build toy apps with it. btw, most of the bugs presented here have at least 4 months...this is really bad because there are several guys here that have identified several bugs (and even lost their time trying to suggest a fix). the minimum the atlas team could do is to give feedback on the status of the problems detected here...

btw, just another suggestion, i really think the team should pass the message that atlas is more than updatepanels surrounding server controls...after using it (and these forums) for several months, it still looks like the wrong message is being passed from the team (ie, you can build ajax apps from the server side - to me this is simply wrong, wrong and wrong again).

just one more thing: to me, it makes more sense to solve all the bugs that have been identified and then extend the platform with more components (as you know, there's been several releases of extra components - atlas toolkit - but the main problems haven't been solved yet).

thanks.

Re: Unofficial bug/issue list for the Atlas CTP

tholewis — Mon, 31 Jul 2006 15:11:27 GMT

The reason you are seeing bugs is that Atlas has not been released. It is still a community technology preview that allows folks to use Atlas and provide feedback to the product team.

Re: Unofficial bug/issue list for the Atlas CTP

albertpascual — Mon, 31 Jul 2006 14:45:54 GMT

Why there are so many bugs on Atlas? How after that long cannot get it right? There are other people like telerik.com or componentsart that got a working version of AJAX controls without problems. It just does not make any sense.

My 2 cents again

Re: Unofficial bug/issue list for the Atlas June CTP

Luis Abreu — Mon, 31 Jul 2006 11:34:38 GMT

hello.

well, currently this is it!

Re: Unofficial bug/issue list for the Atlas June CTP

Jokin.c — Mon, 31 Jul 2006 10:49:53 GMT

I don't know if this is the correct place to post an issue, but i have a problem with firefox, the OnApplicationLoad event isn't fired, and the code that initialize the page don't work with firefox.

¿where is the official bug tracker?

Re: Unofficial bug/issue list for the Atlas June CTP

Luis Abreu — Mon, 31 Jul 2006 10:29:23 GMT

howdy.

two more nasting bugs...

http://forums.asp.net/1355881/ShowThread.aspx#1355881
http://forums.asp.net/thread/1355860.aspx

i'm starting to think that maybe it's better to go try something else...

Re: BUG #12

noahwsmith — Thu, 27 Jul 2006 15:55:01 GMT

AHA! I found this issue, it was reported as an toolkit/extension issue here. I'll post there to point out that it is a WebParts issue too.