Beyond doing the obvious I've also tried to put in some size management and logic for doing component destruction.Performance for a small number of records is absolutely fine but it should come as no surprise that it doesn't scale particularly well.Properties added: Border Margins, Controls Padding X, Controls Padding Y[-] TLMDFlow Panel.Several aligning issues fixed;[-] LMDThemes Gradient Theme Base: gradient arrow rendering fixed; several small fixes;[-] TLMDBase Graphic Button.Your code registers itself with Share Point to be called whenever an event occurs, such as a list is being deleted or a list item is being added.With full trust code solutions, you would register your code by giving Share Point an assembly name and type name.Null Reference Exception: Object reference not set to an instance of an object. Deleting the field and recreating it fixed the issue, but I didn’t want to go there because there were a lot of documents with version history already using the field.
This documents contains history logs for all LMD-Tools 2010 products (except LMD El Pack and LMD IDE-Tools packages).
I know a lot of people have written custom code to do this sort of thing but as far as I'm aware no-one has ever wrapped it up in a reusable class.
28495 The technique will be familiar to anyone who has tried to do it themselves: render the grid without the components then slip the components in afterwards.
Sharepoint Tips And Tricks is Ishai Sagi's sharepoint information blog.
It specializes in Microsoft Share Point technologies, including web parts, development, configuration, customization, and best practices for the use of Microsoft Share Point Server and Windows Share Point Services.