Calling the Predefined Dialogs from the Server Methods | RadWindow for ASP.NET AJAX Documentation
Edit this page

Calling the Predefined Dialogs from the Server Methods

The server-side methods that call the RadAlert, RadConfirm and RadPrompt dialog boxes were added in Q1 2011. They allow the developer to call these popups from the code-behind without having to inject the script himself/herself. This, however, cannot override their JavaScript nature, so essentially these server-side methods must go through JavaScript to show the predefined dialogs.

Escaping for JavaScript

The above means that when preparing the string that will be shown to the end user it must be properly escaped for JavaScript as well. A prime example for this are apostrophes (sometimes known as single quotes). They are string delimiters in JavaScript and so their presence would terminate the string too early and throw a JavaScript error. They must be escaped either with a backslash, or with their HTML entity.

There are other symbols that need escaping, for example a backslash (which is a special character in both JavaScript and C#), so an easy approach is to replace all its instances with its HTML entity: & # 9 2 ; (there are spaces here so that your viewing agent does not convert it to the actual symbol). This will also spare the need to escape it for C# itself. Note, however, that in C# you would need two backslashes to escape a single apostrophe – the first would escape the second for C# so that the second can escape the apostrophe in JavaScript.

Using HTML content

There is also the fact that you can place HTML in the message, but it must be valid so that it does not break the rest of the page by, for example, closing another tag too early. Generally a good approach would be to escape your HTML fully, for example by using the HtmlEncode() method the .NET framework offers. Note that this should be done before transforming any other special characters to HTML entities, as HtmlEncode() would transform the ampersand of the entity to its own entity which would prevent the browser from reading it properly.

Since the displayed string is finally HTML this means that environmental variables such as new lines must be configured for HTML – this is the <br /> tag and not \r, \n, vbCrLf, CR, LF, chr(10) or chr(13) as is in C# and VB. In this regard the String.Replace() method is often useful and quite straightforward to use.

Is this article helpful? No Yes
Thank you for your feedback!

Give article feedback

Tell us how we can improve this article