That's what I was thinking too. But it seems that if my dll methods are
anything but public then my application can't access them due to improper
access level.
It looks like there is a work around with strong names, internal methods and
the InternalsVisibleTo attribute but this involves some fancy sdk stuff that
I am not having successs with. I can make the sdk files but I can get "sn -t"
to work. The fact is, this isn't C# stuff, it's more complicated and I don't
feel comfortable with it.
[quoted text, click to view] "Stevanich" wrote:
> mr peanut,
>
> This is more of a coding question, but you want to look at access modifiers
> (Public, Private, Protected, Friend, etc.)
>
> Hope this helps,
>
>
> Steve - dotneticated.com
>
> "mr peanut" <mrpeanut@discussions.microsoft.com> wrote in message
> news:579DB27A-4FE8-4999-B29D-11A3FFC801DC@microsoft.com...
> > My application references a class library dll. When deployed, the dll
> > appears
> > to be importable as a reference for other programs and the methods are
> > visible to users installing the application (provided they have VS).
> >
> > I checked and I found several applications on my home computer that have
> > transparent dlls like this - some of them pretty expensive.
> >
> > How do I make the methods in my dll's hidden and unavailable to others?
> >
>
>
mr peanut,
This is more of a coding question, but you want to look at access modifiers
(Public, Private, Protected, Friend, etc.)
Hope this helps,
Steve - dotneticated.com
[quoted text, click to view] "mr peanut" <mrpeanut@discussions.microsoft.com> wrote in message
news:579DB27A-4FE8-4999-B29D-11A3FFC801DC@microsoft.com...
> My application references a class library dll. When deployed, the dll
> appears
> to be importable as a reference for other programs and the methods are
> visible to users installing the application (provided they have VS).
>
> I checked and I found several applications on my home computer that have
> transparent dlls like this - some of them pretty expensive.
>
> How do I make the methods in my dll's hidden and unavailable to others?
>
