Can someone give me step-by-step instructions for associating a custom
editor and designers with controls in a WinCE5.0 Control Library?
At http://www.mooseworkssoftware.com/VS2005%20Control.htm I found this:
"...we set the Editor attribute of the class to that editor as shown
below."
<Editor>
<Type>Mooseworks.GI.SimpleGraphEditor, MwSimpleGraphEditor,
Version=1.0.0.0, Culture=neutral,
PublicKeyToken=15EF1E3443EA1F6B</Type>
<BaseType>System.ComponentModel.ComponentEditor, System,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089</BaseType>
</Editor>
Easy, right? "
I don't see anything easy about it. Where does all that information
come from?
kevin cline - 28 Oct 2005 22:16 GMT
Ok, I figured out that you can get that information via gacutil /l
Tim Wilson - 28 Oct 2005 22:23 GMT
You need to build your editor(s) and designer(s) into an assembly (dll)
through a .NET 2.0 class library project (a full framework project, not a
compact framework project). You then compile this full framework class
library assembly ensuring that it's strong named using a generated key (this
can be easily done in VS 2005 through the project properties). This assembly
will need to be installed into the GAC (gacutil /i [assembly name]). Once
the assembly is installed into the GAC you can view all the information that
you need to indicate the "Editor" tag within the xmta file. The information
is accessible within the GAC by right-clicking on the assembly and viewing
its properties.
Note that when creating a custom designer for a smart device custom control
you should inherit from the
Microsoft.CompactFramework.Design.DeviceControlDesigner type which is
located in the Microsoft.CompactFramework.Design.dll assembly.

Signature
Tim Wilson
.NET Compact Framework MVP
> Can someone give me step-by-step instructions for associating a custom
> editor and designers with controls in a WinCE5.0 Control Library?
[quoted text clipped - 17 lines]
> I don't see anything easy about it. Where does all that information
> come from?