When I work with the tab Ajax control, and in one tab, I have a Repeater: <asp:Repeater runat="server" ID="rp1" onitemcommand="rp1_ItemCommand"> and in protected void rp1_ItemCommand(object source, RepeaterCommandEventArgs e) method, I add a button and it's event:
I'm using an AjaxToolKit Accordion Control and when I put a button in, the "onclick" event is not raising. When I use a dropDownList, if I select "autoPostBack", the event raises normaly (instead, nothing occours). But with buttons I cannot define the "autoPostBack" (its implicit?).
I have a script that runs during the Page_Load() event which checks a database table to make sure that the user is still owns the lock on the page. If they no longer own the lock, I disable all the controls on the page and display an error message.My thinking was that by disabling all controls during Page_Load() I could prevent any PostBack events from occuring. For example, I have a button on the page called "Save and Quit"
End TryWhen I run the application in debug mode, the Response.Redirect statement raises an exception. When I have breakpoint to find out the Ex.Message, it says "Expression cannot be evaluated at this time."
configure the .Net HttpWebRequest object so that it does not raise an exception when HttpWebRequest.GetResponse() is called and any 300 or 400 status codes are returned?
Jon Skeet does not think so, so I almost dare not even ask, but I find it hard to believe there is no way around this. 300 and 400 response codes are valid responses in certain circumstances. Why would we be always forced to incur the overhead of an exception?
Perhaps there is some obscure configuration setting that evaded Jon Skeet? Perhaps there is a completely different type of request object that can be used that does not have this behavior?
(and yes, I know you can just catch the exception and get the response from that, but I would like to find a way not to have to).
I have 2 web user controls, both inherit the same base class which extends UserControl. I want to raise an event on one and the other should be aware of it. both are on the same page however the 2nd control never handles the custom event i raised on the 1st one !
i'm trying to learn about user controls. I created a user control that has a textbox and a button. What i'd like to be able to do is when i click the button in the user control, populate a label in the aspx page. I understand that i could just have a button on the page that uses some properties on the user control to get that information.. but i'd like to know how to do it with the button the user control.. the reason for this is the button is just an example.. a learning tool. if i can get this working, i'd likely be putting thing in the user control that might require this kind of passing information. Anyway.. i've found some c# examples that i tried to get working as vb.. but once started getting into the delegates and events.. well.. it made me turn to this post.
I use SqlWebEventProvider to log the exceptions to sql server, and it works fine.
I also want to log custom exceptions to aspnet_WebEvent_Events table programmatically. Similar to - [URL]
WebBaseEvent.Raise(new WebErrorEvent("My Error message", null, 5000, e)); I get an error saying "Cannot access constructor 'WebErrorEvent' here due its protection level.
I have a list of events that have been retrieved from a database a bit like this: Easter St Patrick's Day Christmas Independence Day ... I would like to make them links and when you click on the link it raises a modal popup and displays a bit more information from the database about the event. So far, I've set up the ModalPopupExtender like this on my page:
[Code]....
I thought the links might look something like this:
I'm not quite sure how well this will repeat though. It looks like I'll have to have a ModalPopupExtender for every single link which doesn't sound very efficient. Am I doing this right?
i have the following problam:i have a user control which i want to raise an event from to the page that is using that user control (its a button)anyway my problem started when i wanted to put this user control inside a repeater instead of another button (regular asp:button) anyway i needed to support CommandArgument so that page can use the buttonso i created a property:
Private m_CommandArgument As Object Public Property CommandArgument() As Object Get
I have a url whose query strings are concatenated based on selected items on a form, I need to do a post to this url, but an imagebutton control has to be clicked for the post to occur. I put the PostBackUrl property of the imagebutton inside the event of the image button, hence causing it to be clicked twice before eventually posting the url... but i really need to click once but this aint working. I know why its clicking twice, tried calling the url with javascript but it wasnt working.
I have a button that has an server side event onclick that when triggerd adds javascript code to the onclick event and changes the text value.
On the second click only the javascript code is triggered who changes the text value of the button and sets the client side onclick event to null, while resoponding wiht an return false to counter the postback.
On a real postback of my page the button text value is set back to the latest value given by server side code, it does not keeps its properties set by the javascript client code.
I think this is normal as the button is not posted back or something like that. How could I keep its client side changed properties and let the server side know about it ? Can I modify the viewstate or something similar .... ?
I have a set of radio buttons for "yes" and "no" values which have a name="choice". "yes" is checked by default. They're both runat="server". I read the choice on postback like below. It works perfectly fine as long as the validation doesn't fail. For example, if I select "no" and validation fails on postback, I still see "no" selected. But if I submit the form after correcting everything, the value read is "yes" on server side! Is this a bug in .net, and if so, how do i fix this?
foreach (string key in Request.Form.AllKeys) { if (key.EndsWith("choice")) return Request.Form[key] == "yes"; }
I'm using Javascript to create a DIV element and open up a new page by using onclientclick. This works great. Now, I need to write to it from the server side and this element must be created before it is posted back.
How do I get the javascript to execute before the postback?
Currently, I have to press the button twice because the element doesn't exist to write too on the first click.
To be clear, I need this to execute before the "OnClick" of the button.
Update: It looks like the Javascript function is called before the postback but the element is not updated until I run the second postback.
Update: Unfortunately it is a bit more complicated then this.
I'm creating a div tag in javascript to open a new window. Inside the div tag, I'm using a databinding syntax <%=Preview%> so that I can get access to this element on the server side. From the server side, I'm injecting the code.
I'm thinking this may be a chicken-egg problem but not sure.
UPDATE!
It is not the Javascript not running first. It is the databinding mechanism which is reading the blank variable before I'm able to set it.
I am writing a ASP program which I am going to run on an IPAD. Created a numeric keypad using buttons. Click a button and it adds the value to a textbox. textbox.text = textbox.text + "1"
Having some delay after each button press. I think this is due to postback happening with each keypress.
Is there a way that I can click a button...have it add the value to textbox.text and not do a postback? In other words do everything on the client side. It is my understanding you can run a Java script on client side but I don't know much about java at this point.
I have a button whose sole purpose is to set div.visible = true
There is a calendar control on my page and I need the selected date to remain selected after I hit this button. Right now if I hit the button it refreshes the whole page and sets the calendar's selected day back to date.