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?
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?