DLL Reference Problem

[JK]

I have a DLL that I created to include in all of my apps. However, once I included it my apps still don't recognize the functions or the sub routines in the dll. I am new to dot net and the only thing I can come up with is that I am referencing the dll wrong. Any suggestions?

[Jay B. Harlow [MVP - Outlook]]

JK,
You need to be certain to put Public on every element that you want to
access from the second assembly. Also consider either Friend or Private for
elements that you don't want the second assembly to access.

Protected is useful for elements in base classes to be used by derived
classes.

I normally explicitly label elements as Public or Private rather then
relying on the defaults.

Hope this helps
Jay

"JK" <an*******@discussions.microsoft.com> wrote in message
news:EC**********************************@microsof t.com...

I have a DLL that I created to include in all of my apps. However, once I

included it my apps still don't recognize the functions or the sub routines
in the dll. I am new to dot net and the only thing I can come up with is
that I am referencing the dll wrong. Any suggestions?

[Ken Tucker [MVP]]

Hi,

Only public functions, sub routines, classes, and modules will be
available outside the dll.

Ken
--------------
"JK" <an*******@discussions.microsoft.com> wrote in message
news:EC**********************************@microsof t.com...

I have a DLL that I created to include in all of my apps. However, once I
included it my apps still don't recognize the functions or the sub routines
in the dll. I am new to dot net and the only thing I can come up with is
that I am referencing the dll wrong. Any suggestions?

[Herfried K. Wagner [MVP]]

* "=?Utf-8?B?Sks=?=" <an*******@discussions.microsoft.com> scripsit:

I have a DLL that I created to include in all of my apps. However,
once I included it my apps still don't recognize the functions or the
sub routines in the dll. I am new to dot net and the only thing I can
come up with is that I am referencing the dll wrong. Any suggestions?

Maybe you'll have to import the namespace of the DLL: Add 'Imports
<Namespace name>' on top of your source files. You can change the root
namespace of the DLL in its project options. If you are using modules
in the DLL: Use classes with public shared methods instead.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[JK]

None of these suggestions help.