VS2010 support is tricky because GrowlNotifications.xaml uses new types & theme resource keys introduced in VS2012.
This will probably involve separate ControlTemplates or DataTemplates for the Border in the existing DataTemplate, with two versions of the UI for 2010 & 2012+, but only a single copy of the set of triggers.
It will probably also take some conditional MSBuild magic to make it build in 2010. (and 2010 will probably not be able to produce a build for later versions, unless I require a later SDK or include DLLs.
VS2010 support is tricky because GrowlNotifications.xaml uses new types & theme resource keys introduced in VS2012.
This will probably involve separate
ControlTemplates orDataTemplates for theBorderin the existingDataTemplate, with two versions of the UI for 2010 & 2012+, but only a single copy of the set of triggers.It will probably also take some conditional MSBuild magic to make it build in 2010. (and 2010 will probably not be able to produce a build for later versions, unless I require a later SDK or include DLLs.