Thanks for the reply Juan but...

S

sorCrer

Hi Juan,

Thanks for the reply!

Unfortunately your answer didn't help me. If I don't 'Import' the
custom class then I can't call any of it's functions. This problem
goes away if I compile the .vb file first, and import the namespace
and class with an import directive! It's almost as if the framework
can't see the /code directory the way it should.

What drives me crazy is that Studio's intellisense recognises the
namespace in the source file and allows me to import it. It's only
when I run the application that the error pops up.

So a compiled version of the .vb file works fine with the resulting
..dll dropped in the /bin directory. But the uncompiled .vb file in the
/code directory doesn't!

What the hell am I missing?
 
K

Karl Seguin

Sorcrer:
I skipped over your original post to let someone else answer in the hopes
they might be able to help better. I take it you are dealing with VB.Net
2005 and static imports? If so, I agree with you that the behaviour seems
odd/wrong/inconsistent

You can provide feedback on .Net 2005 stuff at:
http://lab.msdn.microsoft.com/productfeedback/ they are very good about
responding.

Karl
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top