Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Windows Forms / Design Time / April 2005

Tip: Looking for answers? Try searching our database.

C# component - Missing properties in VB form

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Frank Kwong - 22 Apr 2005 14:55 GMT
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
Frank Kwong - 22 Apr 2005 15:39 GMT
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
cody - 22 Apr 2005 16:39 GMT
Does the methods/properties have special attributes on it? are they public?

> 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.
[quoted text clipped - 5 lines]
> --
> Message posted via http://www.dotnetmonster.com
Frank Kwong - 22 Apr 2005 17:13 GMT
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;}}
Frank Kwong - 22 Apr 2005 17:38 GMT
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

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.