Best method for creating seperate DataGrid assembly

Aug 11, 2009 at 1:18 PM

I am trying to split the datagrid classes out into their own assembly.  I can get everything to build and run in a little test app, but when the app comes up, it's just a blank white window.  This exact same app targeting the WPF toolkit DLL works fine.  I have essentially copied over all the classes under DataGrid, DataGrid/Primitives, DataGrid/Automation, Themes, and Resources.  Anyone have any pointers or tips?  The key goal here is that we already target a WPFToolkit dll that is out of our control, and we don't want to add another one because everytime it updates we'll have to update it in keeping with the other one we already target.  We just want to utilize the functionality of the datagrid and treat it as it's own control.  Again,  anyone know what I'm doing wrong?

Aug 11, 2009 at 2:51 PM

Are you including the control styles in your custom build? Look at themes\*.xaml.

Aug 11, 2009 at 3:23 PM
mikj wrote:

Are you including the control styles in your custom build? Look at themes\*.xaml.

Yes.  I have both the WPFToolkit-level theme.xamls and the datagrid level theme.xamls.  I edited the toolkit level ones to only look for the datagrid level ones and ignore calendar and datepicker, and as far as I can tell they find it just fine.  I did notice that there is a call in DataGridHeaderBorder to "DataGridHelper.GetTheme" which, in my working app targeting the WPFToolkit DLL gets called fine, and in my identical app targeting the datagrid-only DLL, does not get called at all.  I can't figure out where it's getting called from, somewhere in xaml.  I'm going to continue investigating, but if this means anything to anyone more well versed in these classes, let me know :)