Design-time Components

[Jeffrey Huntsman]

Hello. I have been having a helluva time trying to convert some custom
controls that I have developed into a design-time assembly.

I have been following the article at
http://msdn.microsoft.com/vstudio/u...en-us/dnnetcomp/html/customctrlscompactfx.asp
exactly, but I cannot get the silly thing to compile for the life of me.

Has anyone actually done this that can point me in the right direction,
sample project maybe?

Thanks,

Jeff Huntsman

 

[Chris Tacke, eMVP]

Take a look at the controls at www.opennetcf.org/forms.asp. Some (not all)
have designer support.

 

[Jeffrey Huntsman]

Thanks for the link. I was reading a great article linked from there which
helped me out a bunch (http://www.intelliprog.com/articles/index.html) .
Now, I am still getting a few warnings, but the project is finally
compilable. I am just wondering, are these warnings normal, or is there a
way to get rid of them??

<snip sample warnings>
warning CS1595: 'System.Windows.Forms.Control' is defined in multiple
places; using definition from 'c:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll'


'System.Windows.Forms.HorizontalAlignment' is defined in multiple places;
using definition from 'c:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll'

</snip sampe warnings>

Jeff

 

[Neil Enns [MSFT]]

Those warnings are normal, you can just ignore them. It's because you had to
add references to both the CF and real desktop versions of the Forms
assembly for the design-time control. As long as the CF version is getting
picked up (which the warnings indicate is the case) this is working as it
should.

--
Neil Enns
Lead Program Manager
Microsoft Mobile Devices Product Group

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jeffrey Huntsman]

Ok, thanks for clarifying that.

Also, thanks to everyone. I'm on the right track now!

Jeff

 

[Jeffrey Huntsman]

BTW:

I did notice something peculiar in VS.NET. Sometimes, the environment would
change my reference to System.Windows.Forms in my design-time project to the
CompactFramework\System.Windows.Forms. It would not do it everytime, but if
I restarted VS.NET, then compiled it would build. However, subsequent builds
would change my reference and cause errors.

I solved this by using a custom batch file to build my design-time, but I
thought you might want to know. Hopefully, design-time support in Whidbey
will be improved to make it easier to build user controls in the Compact
Framework (hint-hint).

Thanks again,

Jeff Huntsman (MCSD.NET)