I downloaded VS 2010 yesterday because I wanted to see the new improvements in the ADO.NET Entity Framework.
Created a test Dynamic Data Entities site and changed the routes to use ListDetails instead of List|Details|Edit|Insert.
What I've found is that LinkButtons nested inside data control templates (such as a FormView ItemTemplate or GridView Column) are causing full postbacks when the data control is nested inside an UpdatePanel.
So, if I navigate to MySite/EntityName/ListDetails.aspx and click the Edit link for any column in the GridView, a full postback occurs.
I tried creating my own custom pages and found the same problem. On some of them, simply changing the control from asp:LinkButton to asp:Button solved the problem (Buttons caused partial postbacks whereas LinkButton in same location caused a full postback).
Is this a beta bug that will be fixed in the March release, or am I missing something?
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
for that you can do this way please add commandname and commandargument in the linkbutton and take rowcommand(For GridView) or itemCommand(For Datalist/Repeater) event and add AsyncPostBackTrigger in the updatepanel.
For this you can refer this link
http://forums.asp.net/p/1497248/3538905.aspx
Thanks & Regards
Vipul Donga
Mark it as an answer, if it helped
if (MyAnswer)
MarkAsAnswer();
else
Repsonse.Write("correct me where i am wrong");
But what if the LinkButton is actually contained in a UserControl? I don't think you can reference an AsyncPostBackTrigger unless the UpdatePanel can see the control (i.e. in the same NamingContainer). The ChildrenAsTriggers=true and UpdateMode=Always should
mean I don't have to specify an AsyncPostBackTrigger.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
What I've found is that LinkButtons nested inside data control templates (such as a FormView ItemTemplate or GridView Column)
are causing full postbacks when the data control is nested inside an UpdatePanel.
So, if I navigate to MySite/EntityName/ListDetails.aspx and click the Edit link for any column in the GridView,
a full postback occurs.
I tried creating my own custom pages and found the same problem. On some of them, simply changing the control from asp:LinkButton to asp:Button solved the problem (Buttons caused partial postbacks whereas LinkButton in same location caused a full postback).
Is this a beta bug that will be fixed in the March release, or am I missing something?
It is neither bug nor problem.
It is by design and the basic principles of asp.net ajax.
UpdatePanel is server-side Ajax technique
for server (web) controls.
Any processing in it is being done on a server
for which a postback is fired.
The Postback is always fullpage
(unless it is callback, using [webmethod], but then it is not postback).
It is the response which is partial page update ( from server to browser).
The server requires full page class reconstruction if it is postback
(to use asp.net server controls).
I see... so I should decorate the server method being invoked by the LinkButton with the WebMethod attribute? Does this mean that with VS2010 / .NET4, LinkButtons in UpdatePanels will trigger full postbacks by default?
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
I see... so I should decorate the server method being invoked by the LinkButton with the WebMethod attribute? Does this mean that with VS2010 / .NET4, LinkButtons in UpdatePanels will trigger full postbacks by default?
I have strange feeling that I am to answer what I already wrote:
LinkButton is server control (and UpdatePanel is used for server-side ajax),
in order to function it requires fullpage postback
(and full page class reconstruction on server).
[WebMethod] is attribute for method to be called,
not for control.
I must be asking the wrong question, I apologize. I understand the part about full class reconstruction on the server.
What I'm struggling to understand is exactly how this behavior is different in .NET4 than it was in 3.5 and 2.0+Ajax Extensions. I'm used to being able to drop LinkButtons into UpdatePanels and having their click events trigger some kind of partial page
update on the browser. The button click code is in the page class, so I understand that the page class' lifecycle starts anew (Init, Load, PreRender, etc).
As I currently understand it, the UpdatePanel traps and handles the LinkButton's client click event. Instead of the page submitting a fully synchronous HTTP POST request, the UpdatePanel instead creates an XmlHttpRequest and updates the DOM with the corresponding
Xml response from the server. While the page class is handling this request, I get a value of TRUE for the Page.IsPostBack property, as well as a true value for the Page.IsAsync property.
Let's say I have a .NET4 web site and I want to have a LinkButton cause some kind of partial page update when clicked. Where do I attach the LinkButton's click code? On the client click (<a onclick="invokeCallbackMethod"...) or on the server click (<asp:LinkButton
OnClick="OnServerClickHandler")? If the latter, do I just decorate the OnServerClickHandler method with the WebMethod attribute, or are there additional steps I need to take to wire the LinkButton to the server-side callback method?
Thanks for your patience,
Dan
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
What I'm struggling to understand is exactly how this behavior is different in .NET4 than it was in 3.5 and 2.0+Ajax Extensions.
Can you give any references on these differences mentioned?
I can try to explain how it was and I doubt,
from the p.v. of common sense and backward compatibility,
that the principles (model) could have changeв in ASP.NET 4.0
Yes. Create a new Dynamic Data Entities web site using VS 2010 targetting .NET4. Set up the routes to point to the ListDetails.aspx page for all entities, and create some kind of Entity Data Model to pull data from.
When you go to any of the ListDetails.aspx pages (Site/EntityName/ListDetials.aspx), click on any of the LinkButtons in the GridView. These are causing fully synchronous postbacks even though the controls are wrapped in an UpdatePanel.
This is not the same as a VS2008 Dynamic Data Entities web site targeting .NET 3.5, where the LinkButtons in the ListDetails.aspx page cause partial page updates. This was the essence of my initial inquiry.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
Isn't there any answer to this? I've asked the same question in many forums without answer. Is it a bug? The same behaviour applies to the filters in the QueryableFilterRepeater. There is no partial refresh of the page but full refresh!
I'm sorry if I don't understand what the answer is. Let me try to rephrase the question so as to see if it has been answered or not.
I do realize that an UpdatePanel causes a full postback in the server (yes, by design) and a
partial refresh in the client page. So far so good.
Our problem is that having a LinkButton inside an UpdatePanel causes a full postback in the server
AND a FULL refresh of the page in the client. This was not the case in the older version of the framework.
If you want to demonstrate this behaviour you can create a default Dynamic Data Entities Web Application in Visual Studio 2010, browse to any List.aspx page and click any LinkButton that sorts the GridView. You will see that the page refreshes fully (yes,
in the client) even though the GridView is surrounded by an UpdatePanel.
I guess my nomenclature was bad. I was mixing the terms "PostBack" and "Page Update" incorrectly. Thanks for clearing that up kkara.
If this guy says "it's by design" one more time I'm gonna get Scott Gu over here to set us ALL straight. This CANNOT be by design. Ignoring our posts does not make this problem go away! I've already given up on .NET4 and VS2010 just because of this problem.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
I am saying this in response to the title of the topic and absence of clear or, even, any definitions in a post. You skewed and screwed this discussion from the very beginning,
you should just open another thread/topic and not continuing under incorrect title at all.
I do not work in this area and I am not interested to study this question
but what I am starting to read is always spurious statements starting from the title.
Create a new Dynamic Data Entities web site using VS 2010 targetting .NET4.
Is Dynamic Data Entities essential to teproduce this bug?
Why, then, you title/tie all the topic to LinkButton (causing...)? and incorrect questioning?
Look dude, if I knew what was causing this to happen I wouldn't have written a thread about it. If it's not your area of expertise, why did you reply? Just to correct my wording? I think most people would know what I meant when I say "full page postback"
versus "partial postback" in the context of an UpdatePanel.
I titled this with the term LinkButton because, when I changed the controls from asp:LinkButton to asp:Button, the problem went away. It only seemed to be problematic with LinkButtons. I am so sorry to have mislead you with my "incorrect questioning." Don't
get mad at me just because you don't know the answer.
Good luck finding a job this year.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
I replied because it is public forum with public access to anybody for discussion but not reporting tool.
If you are interested in answer by experts in the field (but not in discussing it),
you should not put your questions in public forum but report the issue/proposal/doubt/bug
using bug more direct channels
directly to MS development team.
Especailly if you are so irritated by attempts to clarify and disambiguate the context of the issue.
I, also, do not have any fault that you blurred the simple issue to such an extent
Does it bother you so much
that you created a new user on the eve of New Year
just to prove someone (me)
to be an idiot not understanding your world-scale-significant worries?
You're absolutely right. I was so frustrated with this enormous problem that I created a new account yesterday and pretended to be someone else to ask this question again, on the same thread, because I have nothing better to do with my time. I have no idea
that beta software can be buggy and I think it should work perfectly because I'm ignorant. Maybe when I turn 12 later this year I'll start acting more mature and stop masquerading under assumed identities to fool others into thinking at least one other person
on this planet shares my woes.
I'm sorry I should have thanked you for the bug reporting link. I will just use that since this does appear to be a bug, and not just something I was doing wrong due to my lack of experience with .NET4 and the new AjaxLibrary. I will report it there, and
I will make sure not to forget there is no such thing as a "partial postback" in my description. I'm sure the smart, hard-working people at Microsoft will get it ironed out before the release, since it should appear to be a glaring hole in the software to
anyone who has taken the time to reproduce it.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
Have you posted this as a bug in the bug reporting link? If so, could you please post a link to it? I am VERY interested in seing this resolved so I would like to see what the Microsoft guys will say. Thanx a lot.
Could be, I hadn't checked the ScriptResource.axd in the rendered source. But even so, the DynamicData routes worked with UpdatePanels in .NET 3.5, and the asp:Button controls did async postbacks. If the Microsoft AJAX Framework scripts were being excluded
because of the DynamicData routes, how could the Button behave as expected inside an UpdatePanel? It doesn't change the routes.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
I experienced this problem too. Was not using DynamicData at all. But I *was* using a master page, which they mention in the MS Connect bug. I'm actually shocked by this. Update panels and master pages have been around forever. It must have just been seriously
rewritten. I've experienced more issues with VS 2010 than I have with all other versions of VS combined. I hope they get it all working with the RC.
Note: While attempting to post the above I got:
Unfortunately an error has occurred during the processing of your page request. If you were attempting to submit a new post, your post may not have been recorded. Please accept our apologies for the inconvenience.
Check to ensure that the control that is firing the postback has an ID tag. Good chance it doesn't, especially if you are just playing around with new technology to try it out. If a subcontrol does not have an ID, then it will cause a full page refresh.
I have no idea if this is by design or not, but it definitely causes the problem consistently.
The controls did have an ID attribute set in markup. I filed a MS Connect bug report, and learned that this behavior does not exist in their most recent builds. It will be fixed in the February CTP, I am told.
My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
Participant
1985 Points
585 Posts
LinkButton causing full postback in UpdatePanel ...?
Dec 14, 2009 01:30 AM|danludwig|LINK
I downloaded VS 2010 yesterday because I wanted to see the new improvements in the ADO.NET Entity Framework.
Created a test Dynamic Data Entities site and changed the routes to use ListDetails instead of List|Details|Edit|Insert.
What I've found is that LinkButtons nested inside data control templates (such as a FormView ItemTemplate or GridView Column) are causing full postbacks when the data control is nested inside an UpdatePanel.
So, if I navigate to MySite/EntityName/ListDetails.aspx and click the Edit link for any column in the GridView, a full postback occurs.
I tried creating my own custom pages and found the same problem. On some of them, simply changing the control from asp:LinkButton to asp:Button solved the problem (Buttons caused partial postbacks whereas LinkButton in same location caused a full postback).
Is this a beta bug that will be fixed in the March release, or am I missing something?
Contributor
2380 Points
688 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 14, 2009 02:43 AM|vipuldonga|LINK
hi,
for that you can do this way please add commandname and commandargument in the linkbutton and take rowcommand(For GridView) or itemCommand(For Datalist/Repeater) event and add AsyncPostBackTrigger in the updatepanel.
For this you can refer this link
http://forums.asp.net/p/1497248/3538905.aspx
Vipul Donga
Mark it as an answer, if it helped
if (MyAnswer)
MarkAsAnswer();
else
Repsonse.Write("correct me where i am wrong");
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 14, 2009 02:52 AM|danludwig|LINK
But what if the LinkButton is actually contained in a UserControl? I don't think you can reference an AsyncPostBackTrigger unless the UpdatePanel can see the control (i.e. in the same NamingContainer). The ChildrenAsTriggers=true and UpdateMode=Always should mean I don't have to specify an AsyncPostBackTrigger.
ASPX Web Page
--> UpdatePanel
--> FormView
--> ItemTemplate
--> UserControl
--> LinkButton
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 14, 2009 09:09 PM|guenavan|LINK
It is neither bug nor problem.
It is by design and the basic principles of asp.net ajax.
UpdatePanel is server-side Ajax technique
for server (web) controls.
Any processing in it is being done on a server
for which a postback is fired.
The Postback is always fullpage
(unless it is callback, using [webmethod], but then it is not postback).
It is the response which is partial page update ( from server to browser).
The server requires full page class reconstruction if it is postback
(to use asp.net server controls).
http://stackexchange.com/users/68767/?tab=accounts
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 15, 2009 01:57 AM|danludwig|LINK
I see... so I should decorate the server method being invoked by the LinkButton with the WebMethod attribute? Does this mean that with VS2010 / .NET4, LinkButtons in UpdatePanels will trigger full postbacks by default?
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 15, 2009 02:31 AM|guenavan|LINK
I have strange feeling that I am to answer what I already wrote:
LinkButton is server control (and UpdatePanel is used for server-side ajax),
in order to function it requires fullpage postback
(and full page class reconstruction on server).
[WebMethod] is attribute for method to be called,
not for control.
http://stackexchange.com/users/68767/?tab=accounts
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 15, 2009 01:09 PM|danludwig|LINK
I must be asking the wrong question, I apologize. I understand the part about full class reconstruction on the server.
What I'm struggling to understand is exactly how this behavior is different in .NET4 than it was in 3.5 and 2.0+Ajax Extensions. I'm used to being able to drop LinkButtons into UpdatePanels and having their click events trigger some kind of partial page update on the browser. The button click code is in the page class, so I understand that the page class' lifecycle starts anew (Init, Load, PreRender, etc).
As I currently understand it, the UpdatePanel traps and handles the LinkButton's client click event. Instead of the page submitting a fully synchronous HTTP POST request, the UpdatePanel instead creates an XmlHttpRequest and updates the DOM with the corresponding Xml response from the server. While the page class is handling this request, I get a value of TRUE for the Page.IsPostBack property, as well as a true value for the Page.IsAsync property.
Let's say I have a .NET4 web site and I want to have a LinkButton cause some kind of partial page update when clicked. Where do I attach the LinkButton's click code? On the client click (<a onclick="invokeCallbackMethod"...) or on the server click (<asp:LinkButton OnClick="OnServerClickHandler")? If the latter, do I just decorate the OnServerClickHandler method with the WebMethod attribute, or are there additional steps I need to take to wire the LinkButton to the server-side callback method?
Thanks for your patience,
Dan
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 15, 2009 02:00 PM|guenavan|LINK
Can you give any references on these differences mentioned?
I can try to explain how it was and I doubt,
from the p.v. of common sense and backward compatibility,
that the principles (model) could have changeв in ASP.NET 4.0
http://stackexchange.com/users/68767/?tab=accounts
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 15, 2009 02:09 PM|danludwig|LINK
Yes. Create a new Dynamic Data Entities web site using VS 2010 targetting .NET4. Set up the routes to point to the ListDetails.aspx page for all entities, and create some kind of Entity Data Model to pull data from.
When you go to any of the ListDetails.aspx pages (Site/EntityName/ListDetials.aspx), click on any of the LinkButtons in the GridView. These are causing fully synchronous postbacks even though the controls are wrapped in an UpdatePanel.
This is not the same as a VS2008 Dynamic Data Entities web site targeting .NET 3.5, where the LinkButtons in the ListDetails.aspx page cause partial page updates. This was the essence of my initial inquiry.
None
0 Points
13 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 31, 2009 05:34 AM|kkara|LINK
Hi,
Isn't there any answer to this? I've asked the same question in many forums without answer. Is it a bug? The same behaviour applies to the filters in the QueryableFilterRepeater. There is no partial refresh of the page but full refresh!
Kostas
dynamic data UpdatePanel
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 31, 2009 05:44 AM|guenavan|LINK
Ignoring answers does not mean their absence
It is not bug.
It is by design
http://stackexchange.com/users/68767/?tab=accounts
None
0 Points
13 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 31, 2009 05:54 AM|kkara|LINK
I'm sorry if I don't understand what the answer is. Let me try to rephrase the question so as to see if it has been answered or not.
I do realize that an UpdatePanel causes a full postback in the server (yes, by design) and a partial refresh in the client page. So far so good.
Our problem is that having a LinkButton inside an UpdatePanel causes a full postback in the server AND a FULL refresh of the page in the client. This was not the case in the older version of the framework.
If you want to demonstrate this behaviour you can create a default Dynamic Data Entities Web Application in Visual Studio 2010, browse to any List.aspx page and click any LinkButton that sorts the GridView. You will see that the page refreshes fully (yes, in the client) even though the GridView is surrounded by an UpdatePanel.
I hope I made myself clearer now.
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Dec 31, 2009 01:09 PM|danludwig|LINK
"That's what I was tryin' to tell you before!"
I guess my nomenclature was bad. I was mixing the terms "PostBack" and "Page Update" incorrectly. Thanks for clearing that up kkara.
If this guy says "it's by design" one more time I'm gonna get Scott Gu over here to set us ALL straight. This CANNOT be by design. Ignoring our posts does not make this problem go away! I've already given up on .NET4 and VS2010 just because of this problem.
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 01:55 AM|guenavan|LINK
I am saying this in response to the title of the topic and absence of clear or, even, any definitions in a post. You skewed and screwed this discussion from the very beginning,
you should just open another thread/topic and not continuing under incorrect title at all.
I do not work in this area and I am not interested to study this question
but what I am starting to read is always spurious statements starting from the title.
If it is a bug,
there is nothing to discuss,
report it
https://connect.microsoft.com/VisualStudio
and provide a link to that report to others
http://stackexchange.com/users/68767/?tab=accounts
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 02:10 AM|guenavan|LINK
Is Dynamic Data Entities essential to teproduce this bug?
Why, then, you title/tie all the topic to LinkButton (causing...)? and incorrect questioning?
http://stackexchange.com/users/68767/?tab=accounts
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 04:00 AM|danludwig|LINK
Look dude, if I knew what was causing this to happen I wouldn't have written a thread about it. If it's not your area of expertise, why did you reply? Just to correct my wording? I think most people would know what I meant when I say "full page postback" versus "partial postback" in the context of an UpdatePanel.
I titled this with the term LinkButton because, when I changed the controls from asp:LinkButton to asp:Button, the problem went away. It only seemed to be problematic with LinkButtons. I am so sorry to have mislead you with my "incorrect questioning." Don't get mad at me just because you don't know the answer.
Good luck finding a job this year.
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 04:51 AM|guenavan|LINK
I replied because it is public forum with public access to anybody for discussion but not reporting tool.
If you are interested in answer by experts in the field (but not in discussing it),
you should not put your questions in public forum but report the issue/proposal/doubt/bug
using bug more direct channels
directly to MS development team.
Especailly if you are so irritated by attempts to clarify and disambiguate the context of the issue.
I, also, do not have any fault that you blurred the simple issue to such an extent
I gave you the link above
http://stackexchange.com/users/68767/?tab=accounts
Participant
1566 Points
1614 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 05:02 AM|guenavan|LINK
Does it bother you so much
that you created a new user on the eve of New Year
just to prove someone (me)
to be an idiot not understanding your world-scale-significant worries?
http://stackexchange.com/users/68767/?tab=accounts
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 01, 2010 01:25 PM|danludwig|LINK
You're absolutely right. I was so frustrated with this enormous problem that I created a new account yesterday and pretended to be someone else to ask this question again, on the same thread, because I have nothing better to do with my time. I have no idea that beta software can be buggy and I think it should work perfectly because I'm ignorant. Maybe when I turn 12 later this year I'll start acting more mature and stop masquerading under assumed identities to fool others into thinking at least one other person on this planet shares my woes.
I'm sorry I should have thanked you for the bug reporting link. I will just use that since this does appear to be a bug, and not just something I was doing wrong due to my lack of experience with .NET4 and the new AjaxLibrary. I will report it there, and I will make sure not to forget there is no such thing as a "partial postback" in my description. I'm sure the smart, hard-working people at Microsoft will get it ironed out before the release, since it should appear to be a glaring hole in the software to anyone who has taken the time to reproduce it.
None
0 Points
13 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 04, 2010 06:03 AM|kkara|LINK
Hi danludwig,
Have you posted this as a bug in the bug reporting link? If so, could you please post a link to it? I am VERY interested in seing this resolved so I would like to see what the Microsoft guys will say. Thanx a lot.
None
0 Points
1 Post
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 13, 2010 06:24 PM|Busywizy10|LINK
Check this post http://forums.asp.net/t/1512207.aspx
I think you are having the same problem.
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 13, 2010 06:31 PM|danludwig|LINK
Could be, I hadn't checked the ScriptResource.axd in the rendered source. But even so, the DynamicData routes worked with UpdatePanels in .NET 3.5, and the asp:Button controls did async postbacks. If the Microsoft AJAX Framework scripts were being excluded because of the DynamicData routes, how could the Button behave as expected inside an UpdatePanel? It doesn't change the routes.
I went ahead and posted feedback at the MS connect site. Here is the link: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=524827#details.
None
0 Points
13 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 18, 2010 09:09 AM|kkara|LINK
It is definitely not the same problem. I have tried this without using DynamicData routes and it shows the same behavior.
Thanx for the link, I'll keep an eye on it. They say it might be fixed in the February RC...
None
0 Points
1 Post
Re: LinkButton causing full postback in UpdatePanel ...?
Jan 22, 2010 03:28 PM|tommyaquinas|LINK
I experienced this problem too. Was not using DynamicData at all. But I *was* using a master page, which they mention in the MS Connect bug. I'm actually shocked by this. Update panels and master pages have been around forever. It must have just been seriously rewritten. I've experienced more issues with VS 2010 than I have with all other versions of VS combined. I hope they get it all working with the RC.
Note: While attempting to post the above I got:
Unfortunately an error has occurred during the processing of your page request. If you were attempting to submit a new post, your post may not have been recorded. Please accept our apologies for the inconvenience.
Irony. :)
None
0 Points
2 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Feb 03, 2010 01:45 PM|acropolis|LINK
Hi guys,
Check to ensure that the control that is firing the postback has an ID tag. Good chance it doesn't, especially if you are just playing around with new technology to try it out. If a subcontrol does not have an ID, then it will cause a full page refresh. I have no idea if this is by design or not, but it definitely causes the problem consistently.
Cheers,
D
Participant
1985 Points
585 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Feb 03, 2010 02:02 PM|danludwig|LINK
The controls did have an ID attribute set in markup. I filed a MS Connect bug report, and learned that this behavior does not exist in their most recent builds. It will be fixed in the February CTP, I am told.
None
0 Points
2 Posts
Re: LinkButton causing full postback in UpdatePanel ...?
Feb 03, 2010 02:13 PM|acropolis|LINK
Good to know -- thanks!
Cheers.