Devexpress method to register base scripts

If for some reason devexpress scripts dont get registered there is a method on the base control to register scripts.

SQL script to set Simple Recovery and Shrink logs for all database

How to Set a DataItemIndex for a devexpress ASPxGridView

To Get a DataItemIndex in an ASPxGridView I suggest you add an unbound column to your ASPxGridView that will contain the row datasource index. Handle the server-side ASPxGridView.CustomUnboundColumnData event to provide data to this column. Use the ASPxGridViewColumnDataEventArgs.ListSourceRowIndex property to get the processed row's datasource index. Then, you can get data from this unbound column by using the server-side ASPxGridView.GetRowValues method. You can use this code to implement this task: After that, use this code to get the row's datasource index by its visible index:

Select distinct on one column but return all rows

ASPxPage Control Cannot unregister UpdatePanel - Post 2

Just had this issue again, this time without using tab pages. it looks like there are issues redirecting from an ASPxGridView row command. The only hack Devxpress can provide so far is re-registering the controls when they are unloaded. this obviously relies on microsoft never changing their code. To sort, all update panels need to reregister when unloaded! I added a method to my base page as follows: then this can be called on ALL updatepanel unloads

How to hide readonly fields from devexpress ASPxGridView inline edit

It appears you can hide controls using the ReadOnly/Visible properties of the edit controls in an ASPxGridView with inline edit mode. Instead you have to change the EditItem template for the column to contain some blank text or a

Intelliesense not working in Visual Studio

Hi Just a quick not to say about issues with intellisense not working in Visual Studio. I had controls registered in the web.config but intellisense was not picking them up. After a bit of searching I found some duplicate entries in the web.config. removing these duplicates sorted the issue. It seems if there are any problems in the web.config file then intellisense wont work.