The type "Microsoft.CompactFramework.Design.UnsafeControl" has no property

Question

I get this error when opening a design view of a form that has Honeywell DecodeControl (for the Honeywell barcode scanner - Dolphin 6100, if anyone is interested).

I killed it to death and did the following:

Added XMTA file with this in it:

<?xml version="1.0" encoding="utf-16"?> <Classes xmlns="http://schemas.microsoft.com/VisualStudio/2004/03/SmartDevices/XMTA.xsd"> <Class Name="Honeywell.DataCollection.WinCE.Decoding.DecodeControl"> <Description></Description> <DesktopCompatible>true</DesktopCompatible> <DesignTimeVisible>true</DesignTimeVisible> </Class> </Classes> 

Set the XMTA build action to "none"

Ignoring the first error still gives me a reference to an object that is not installed on an instance of the object.

It did not help.

After some lengthy googling, this seems to be related to device-specific controls, and this error should supposedly stop anything that could cause instability in the designer ... except that the control works quite successfully for the designer all day at work, then when I get home, it throws it at me. Nothing has changed - the same dev machine, the same device, the same project, the same code as when it was last saved to the workplace.

I don’t even try to debug the device on the desktop or the emulator - I have a device connected via a USB stand.

Literally the only thing that has changed is that the dev machine is connected to my home network via a wireless network instead of CAT5 to work on the network. And I do not see that it is even remotely related to this.

In a more noteworthy note, this control never appeared in the toolbar after I selected "Elements" → check control. Not sure if this is related.

Can anyone shed some light?

I can publish the designer code if necessary.

thanks

Answer 1

It turned out that I was aiming for the wrong structure for the device - VS decided that I needed that I needed to install 3.5 instead of 2.0. Disconnected it, and all is well.

Answer 2

I ran into this error, but it was caused by the fact that I was playing with the MessageBeep API in the form. Despite the fact that this form is in no way associated with my user controls or components, just the presence of this link to the Interop namespace in the form distorted every control in my application and made it impossible to view them in the constructor.

The moral of this story is NOT USED Interact in CE (PInvoke).

It was scary. Just a heads-up for any other miserable soul trying to make a beep.

Answer 3

I have the same problem in VS2102 with WEC2013.

And without P / Invoke, but with a custom control, fully managed .net code. The problem is the Enum properties of my user control. And there is no solution yet.