J
JohnB
Hello
I've had my head in the sand for about the last year and a half. What seems
like a fairly straightforward question to ask and answer for myself has
turned out to be a challenge. Therefore I thought I would pose the question
to the group here. By the way, I looked for answers on the dotnet.faq
group, dotnet.general group, as well as here before I decided to post.
Alright..the question...
If I create a DLL in VB.Net and write classes with source code (methods or
constructors) that expect VB.Net data types...such as Integer or Long ,
etc., will this pose a problem to other .Net languages? From what I've read
and learned in the past about .Net, I would expect it would not cause a
problem, that the data types would become the framework standard datatypes
in the DLL...such as Int32 or Int64, but I had a debate about that with a
co-worker what thought he had read otherwise. So now I question my
assumption. What's the real story?
On a related note, how would remoting a DLL be affected or would it? I know
you can create a separate assembly with an interface class...or something
along those lines.
Thanks in advance for your insights
John
I've had my head in the sand for about the last year and a half. What seems
like a fairly straightforward question to ask and answer for myself has
turned out to be a challenge. Therefore I thought I would pose the question
to the group here. By the way, I looked for answers on the dotnet.faq
group, dotnet.general group, as well as here before I decided to post.
Alright..the question...
If I create a DLL in VB.Net and write classes with source code (methods or
constructors) that expect VB.Net data types...such as Integer or Long ,
etc., will this pose a problem to other .Net languages? From what I've read
and learned in the past about .Net, I would expect it would not cause a
problem, that the data types would become the framework standard datatypes
in the DLL...such as Int32 or Int64, but I had a debate about that with a
co-worker what thought he had read otherwise. So now I question my
assumption. What's the real story?
On a related note, how would remoting a DLL be affected or would it? I know
you can create a separate assembly with an interface class...or something
along those lines.
Thanks in advance for your insights
John