Andrew,
>What I actually try to do is to register those types to be used in the
>Visual Studio designer for some third party controls.
Can't you handle such registration in a setup package?
>It seems to suggest such a thing exists, but doesn't explain how to get
>a hold of it.
It does (in .NET 2.0) but not all languages let you define such a
method.
Mattias

Signature
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.
andrew.miadowicz@gmail.com - 23 Jun 2006 07:42 GMT
Mattias,
The "registration" I'm referring to is really just the process of
letting this particular third party control designer know that my
editors are available for it to use. This registration is not
persisted anywhere outside of the Visual Studio designer memory. In
fact, if I'm not mistaken (I only had so much time to analyze their
source code) the editors that ship with their package only get
registered when one of their controls (that can host such editors) is
instantiated on the Visual Studio designer.
Besides, in my particular case I'm working on a project in which I both
create and use my custom editors, and consequently no installation
takes place, as everything is a part of one big solution.
As far as the "OnLoad" method I am curious to know if C# 2.0 allows me
to define it somehow. Are there any other workarounds?
Thanks,
Andrew