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.
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.
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).
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!
--
Regards,
Luis Abreu
email: labreu_at_gmail.com
EN blog:http://msmvps.com/blogs/luisabreu
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.
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.
kevindente
Member
344 Points
75 Posts
BUG: Action bindings ignore direction
Aug 01, 2006 02:59 AM|LINK
Knut Meltzer
Member
99 Points
19 Posts
Re: Unofficial bug/issue list for the Atlas June CTP
Aug 01, 2006 08:05 AM|LINK
Hi
Can you add this to your list?
http://forums.asp.net/thread/1336716.aspx
tholewis
Member
110 Points
22 Posts
Microsoft
Re: Unofficial bug/issue list for the Atlas CTP
Aug 02, 2006 06:43 PM|LINK
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.
kevindente
Member
344 Points
75 Posts
Re: Unofficial bug/issue list for the Atlas CTP
Aug 02, 2006 10:20 PM|LINK
> 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).
Luis Abreu
All-Star
25674 Points
5369 Posts
MVP
Re: Unofficial bug/issue list for the Atlas CTP
Aug 03, 2006 08:26 AM|LINK
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!
Regards,
Luis Abreu
email: labreu_at_gmail.com
EN blog:http://msmvps.com/blogs/luisabreu
Garbin
Contributor
7428 Points
1507 Posts
ASPInsiders
Re: Unofficial bug/issue list for the Atlas June CTP
Aug 08, 2006 11:03 PM|LINK
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>manicsquirre...
Member
5 Points
1 Post
Another Bug
Nov 06, 2006 06:51 PM|LINK
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.
albertpascua...
All-Star
17520 Points
3475 Posts
MVP
Re: Another Bug
Nov 06, 2006 09:06 PM|LINK
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.
Al
My Blog