Thanks for invitation, I'd be glad to join as a follower. I'm quite interested in using this component so if I come up with some ideas or code fixes, I'll place it somewhere here.
For now, some few more notes I can make right for the moment:
- I've played a bit with unchanged sources and noticed, that if I retarget it to .Net 4.0 (Full), I get critical error just after start, in this line:
if (Handle == 0) throw new Win32Exception(Marshal.GetLastWin32Error()); (it's GlobalHook.InstallHook())
The error reads as "invalid window descriptor" (sorry for back-translating error message from the localized one). After re-compiling for 3.5, again, it starts without troubles.
Just the same, VS2010 has troubles opening demo forms in designer. It says:
"Object of type 'System.String' cannot be converted to type 'System.Drawing.Image'"
at System.ComponentModel.ReflectPropertyDescriptor.SetValue(Object component, Object value)
at System.ComponentModel.ReflectPropertyDescriptor.ResetValue(Object component)
at System.ComponentModel.Design.Serialization.CodeDomSerializer.ResetBrowsableProperties(Object instance)
at System.ComponentModel.Design.Serialization.CodeDomSerializer.Deserialize(IDesignerSerializationManager manager, Object codeObject)
at System.Windows.Forms.Design.ControlCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, Object codeObject)
at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.DeserializeName(IDesignerSerializationManager manager, String name, CodeStatementCollection statements)
If I create my own form from scratch and put the ribbon here, it works nice though.
And yes, I was a bit (well, not a *bit*) inaccurate, saying that after re-compiling for 2.0 it will start in Client profile (I made this conclusion after changing config manually - probably I missed something...). But I'll try to look if it is feasible to
make "client" versions of components by conditionally commenting-out all mentions of "System.Design" namespace members.