Why is that when I loaded into VB a non-visual component written in C#.
Many Design time properties of the component are missing in the VB form?

Thanks,


Frankk

--

Not just the properties are missing. Most of the methods are also missing
in VB.Net. Events are OK, all there. There must be a simple explanation.

Thanks,

Frankk

--

Yes, indeed. They are all public. The C# test form of course can access to
all. Like the following properties. The "Tg" section all there but the
entire "Sim" section is not there. I'm going to start from scratch and see
which is the first property/method to disappear.

[Category("\t\tTg")]
public string ClockTemplate {get {return _clocktemplate;} set
{_clocktemplate = value;}}
[Category("\t\tTg")]
public string IDTemplate {get {return _idtemplate;} set {_idtemplate =
value;}}
[Category("\t\tTg")]
public string SaveDSN {get {return _dsn;} set {_dsn = value;}}
[Category("\t\tTg")]
public string SaveSQL {get {return _sql;} set {_sql = value;}}
[Category("\t\tTg"),TypeConverter(typeof
(Converters.ProviderDropDownConverter))]
public string SaveProvider {get {return _provider;} set {_provider = value;}
}

[Category("\tSim")]
public string IP {get {return _simip;} set {_simip = value;}}
[Category("\tSim")]
public string Port {get {return _simport;} set {_simport = value;}}
[Category("\tSimulation")]
public string CmdPort {get {return _simcmdport;} set {_simcmdport = value;}}

--

Mystery solved. An older version of DLL is stuck in the reference
(lowercase name). Even when a fresh compiled DLL is in the tool bar, that
still stays there when the component is added. Delete that from reference
and add component again (Mix case name) and now it is OK. Just another one
for those long work day problem.

Thanks,


Frankk

--

Does the methods/properties have special attributes on it? are they public?

"Frank Kwong via DotNetMonster.com" <forum@DotNetMonster.com> schrieb im
Newsbeitrag news:248954f5429140c1ba75de9b8b8b09cc@DotNetMonster.com...
[quoted text, click to view]