Prev: Handling Roles end-to-end
Next: about understanding Threads
From: GS on 8 May 2010 03:19
It seems public members of a net assembly exe can not always be visible to
external callers despite adding the required project reference

I do see in class diagram, a public structure, some public delegates and of
course some gui elements as the exe is form class.

the assembly do have declared public interface

it seems, I cant see many public members even if included in the interface
until I make the assembly visible to COM.


is this com visible a must for the .net assembly to use it.


From: Peter Duniho on 8 May 2010 03:53
GS wrote:
> It seems public members of a net assembly exe can not always be visible to
> external callers despite adding the required project reference

It may seem that way, but I'm sure you're mistaken.

> I do see in class diagram, a public structure, some public delegates and of
> course some gui elements as the exe is form class.
>
> the assembly do have declared public interface
>
> it seems, I cant see many public members even if included in the interface
> until I make the assembly visible to COM.

Any members of the assembly that are truly declared as public will be
visible without any COM-specific support being included. The
"COM-visible" setting certainly is not required. It's a red herring.

Post the code that you think has public members that don't show up when
the assembly is referenced, and we'll either be able to point out why
those members aren't actually public, or we'll be able to compile the
code into an assembly that works fine (suggesting that your problem is
not with the code but in how you're using the compiled assembly).

Pete
From: Arne Vajhøj on 8 May 2010 17:47
On 08-05-2010 03:19, GS wrote:
> It seems public members of a net assembly exe can not always be visible to
> external callers despite adding the required project reference
>
> I do see in class diagram, a public structure, some public delegates and of
> course some gui elements as the exe is form class.
>
> the assembly do have declared public interface
>
> it seems, I cant see many public members even if included in the interface
> until I make the assembly visible to COM.
>
> is this com visible a must for the .net assembly to use it.

Public really means public.

How are you checking if the "public" stuff is visible to
external callers?

Arne

From: GS on 10 May 2010 15:47
I think somehow my logon session, solution build(likely the culprit), or
visual studio was corrupted. I restarted the PC, repair the Visual studio.
did all configuration build w/o com visible.

voila,just like you said, I now can access all pubic members


"Peter Duniho" <no.peted.spam(a)no.nwlink.spam.com> wrote in message
news:%23wWTROo7KHA.6072(a)TK2MSFTNGP06.phx.gbl...
> GS wrote:
> > It seems public members of a net assembly exe can not always be visible
to
> > external callers despite adding the required project reference
>
> It may seem that way, but I'm sure you're mistaken.
>
> > I do see in class diagram, a public structure, some public delegates and
of
> > course some gui elements as the exe is form class.
> >
> > the assembly do have declared public interface
> >
> > it seems, I cant see many public members even if included in the
interface
> > until I make the assembly visible to COM.
>
> Any members of the assembly that are truly declared as public will be
> visible without any COM-specific support being included. The
> "COM-visible" setting certainly is not required. It's a red herring.
>
> Post the code that you think has public members that don't show up when
> the assembly is referenced, and we'll either be able to point out why
> those members aren't actually public, or we'll be able to compile the
> code into an assembly that works fine (suggesting that your problem is
> not with the code but in how you're using the compiled assembly).
>
> Pete


 | 
Pages: 1
Prev: Handling Roles end-to-end
Next: about understanding Threads