By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,238 Members | 1,485 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,238 IT Pros & Developers. It's quick & easy.

.Net datatype compatibility

P: n/a
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
Nov 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Take a look at the topic "CLS-Compliant Code" in the online docs.

http://msdn.microsoft.com/library/de...pliantCode.asp

HTH,
Greg
"JohnB" <pr***************@kc.rr.com> wrote in message
news:Oe**************@TK2MSFTNGP12.phx.gbl...
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

Nov 20 '05 #2

P: n/a
Thanks Greg, that was just what I was looking for.

cheers

John

in reply to:
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:Om***************@tk2msftngp13.phx.gbl...
Take a look at the topic "CLS-Compliant Code" in the online docs.

http://msdn.microsoft.com/library/de...pliantCode.asp
HTH,
Greg

Nov 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.