I'm trying to debug some code and have a feeling that my UpdatePanel is disrupting my Silverlight xap control. There are times where my silverlight chart is not rendering and asking the user to download the silverlight plugin.
Has anyone experienced a problem with a .xap file being a child element of an UpdatePanel?
I have never had to put a Silverlight control within an UpdatePanel. Silverlight controls by nature should not be constantly reloaded like an UpdatePanel will want to do. Everytime an UpdatePanel triggers a refresh your Silverlight control will need to reload.
I would recommend removing the Silverlight control from the UpdatePanel if possible because there is nothing that the UpdatePanel adds to the functionality of the Silverlight control. If you need to trigger stuff from your UpdatePanel then just setup javascript hooks to your Silverlight control.
Related
I have an asp.net application where users answer question in a quiz.
After clicking on "next" a new question is loaded with an Ajax Postback.
I am using the RadAjaxPanel Telerik Control. I think it uses the UpdatePanel internally.
Will my users have (viewstate) errors if I publish a new version of the application during they are using the site?
I am having a developed application and everything works perfectly in visual studio 2010 in local machine.but when I deploy my application in IIS7 classic pool mode, the ajax controls are working fine initially.But once postback is happening none of the of Ajax controls are working?
Please help me in this.
What do you mean by none of them are working?
Shot in the dark, you are likely removing and reloading dom elements that you bound to events previously. Once the new dom elements are loaded you will need to rebind any events such as click to them at that point.
I set a reference to AjaxControlToolkit.dll and this added all of the toolkit's controls to my toolbar. I then tried to drag and drop one of the controls to my webform and nothing happened-no error message, no control added to the form. Double clicking the control also did nothing.
The web site compiles with no errors, I also tried to bounce VS2008. I am running Developers Edition on Windows Server 2008.
I was able to add a Script Manager control
This worked w/o issue on my other computers.
Also, make sure you drop the tools into the source tab of your ASP page. As many of these controls has no graphical representation.
Ajaxtoolkit controls in VS2008 are extenders of other controls. Add the parent control first.
I am new to this whole sharepoint and aspx programming. I have developed a sharepoint web part that has a button control. The onclick event is mapped to a method in my web part code. When I click the button the whole page reloads and the web part is rendered again. Is there a way to prevent this reloading of the page? Is there a way to call the function method in the background? Something similar to AJAX.
Thanks,
Jagannath
You can use Ajax, it just requires some sharepoint configuration. Here are a few posts to get you started:
http://weblogs.asp.net/jan/archive/2007/02/26/using-the-ajax-control-toolkit-in-sharepoint.aspx
http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3
Ajax or SilverLight are your only two options for Async operations without a page refresh.
Once you know the tricks needed to get SharePoint and ASP.NET AJAX to work together it's not that difficult.
Here are the steps required:
Ensure the ASP.NET AJAX Extensions are installed on all the front-end web servers (this is not required if you are using .NET 3.5 as the Extensions are included in the Framework)
Update the Web.config file for the SharePoint Application to support ASP.NET AJAX
Ensure any page that is going to use AJAX has a ScriptManager
Use an UpdatePanel or a client-side service call to get updated data and re-render the Web Part
This blog post has some resources from a talk I did on the subject at TechEd Barcelona 2008. These resources should give you the information you need to get started.
http://msmvps.com/blogs/windsor/archive/2008/11/13/teched-emea-resources-and-demos-integrating-asp-net-ajax-with-sharepoint-2007.aspx
In my last job we ended up rewriting the complete ASP.NET stack (forms, controls, validation, postback handling, ajax library etc...) - the reason I was given was that the ASP.NET controls were not accessible enough, not were any of the third party controls that were assessed for the project.
Can anyone point me to good accessible ASP.NET controls that do ajax as well?
Failing that, how would you approach creating accessible, ajax enabled controls?
You could take a look at the 'App_Browsers' feature in .NET.
It gives you the opportunity to hook into the rendering engine for each control. The original intention for this was to be able to alter the HTML output of controls depending on the user's browser - but you can also do it for all browsers.
You could also take a look at these control adapters, which make the normal ASP.NET controls 'CSS Friendly'.