471,315 Members | 1,604 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,315 software developers and data experts.

Adding a new class to a dll

I've got a dll which houses a namespace hierarchy of useful utilities.
I decided that I wanted to add another class to this namespace today. I
then started up the project, copied the class file to the project
directory, clicked add existing item, and added the class. I then
recompiled the dll.
I then removed the reference to the original dll, and re-added the
reference to (what I thought) get the updated dll. The problem though
is that my new class does not show up in the namespace..
I've tried to delete all occurences of the dll, recompile the, remove
the reference and then add it again, but my changes refuse to appear.
I also tried to move the class to a new sub-namespace but this also
does not appear.

Does anyone have any explanation to what I'm doing wrong?

Jan 11 '06 #1
4 1861
Håvard Olerud Eriksen wrote:
I've got a dll which houses a namespace hierarchy of useful utilities.
I decided that I wanted to add another class to this namespace today. I
then started up the project, copied the class file to the project
directory, clicked add existing item, and added the class. I then
recompiled the dll.
I then removed the reference to the original dll, and re-added the
reference to (what I thought) get the updated dll. The problem though
is that my new class does not show up in the namespace..
I've tried to delete all occurences of the dll, recompile the, remove
the reference and then add it again, but my changes refuse to appear.
I also tried to move the class to a new sub-namespace but this also
does not appear.

Does anyone have any explanation to what I'm doing wrong?

Are you sure the new class is in the same namespace as the others?
Did you check if you compiled the Debug/Release version of the new dll
and if it is that one you are trying to use?
Jan 11 '06 #2
Yes, I've doublechecked this. My release version is compiled to a
shared network drive and I've deleted the file, then recompiled to make
sure it's the correct location with the correct timestamp. I've also
compared the namespace names of two "siblings" but afaiks it's all
correct.

Jan 11 '06 #3
Håvard,

Make sure that your class is declared as *public*. Keep in mind that the
default is *internal*, which means they can only be used inside the
assembly.
--
HTH
Stoitcho Goutsev (100)

"Håvard Olerud Eriksen" <ho*******@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
Yes, I've doublechecked this. My release version is compiled to a
shared network drive and I've deleted the file, then recompiled to make
sure it's the correct location with the correct timestamp. I've also
compared the namespace names of two "siblings" but afaiks it's all
correct.

Jan 11 '06 #4
Bingo. That was the one thing I'd overlooked. Thanks a bunch!

Håvard

Jan 12 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Andrew Ward | last post: by
5 posts views Thread by surrealtrauma | last post: by
11 posts views Thread by Steven D'Aprano | last post: by
3 posts views Thread by Gabriele *darkbard* Farina | last post: by
3 posts views Thread by Jim Heavey | last post: by
13 posts views Thread by Rob Meade | last post: by
2 posts views Thread by Dave Calkins | last post: by
11 posts views Thread by Pete Kane | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.