dotnet framework

  • Thread starter Thread starter Carl Forsman
  • Start date Start date
C

Carl Forsman

why dotnet framework can access from so many different languages?

like C, C++, C#, VB, ADA

is that microsoft had developed the component for different language
to access the dotnet functions?

is it just like Java access C++ library / DLL where for each function
you have to map the Java parameters to C++ parameters?

So microsoft had map each of the C, C++, C#, VB, ADA to dotnet library
function - for each of the donet library functions?? just like Java
native interface access C++ native code?

in the low level of dotnet library? is make simple for each function
to map to different languages?
 
Carl Forsman said:
why dotnet framework can access from so many different languages?

like C, C++, C#, VB, ADA

is that microsoft had developed the component for different language
to access the dotnet functions?

is it just like Java access C++ library / DLL where for each function
you have to map the Java parameters to C++ parameters?

So microsoft had map each of the C, C++, C#, VB, ADA to dotnet library
function - for each of the donet library functions?? just like Java
native interface access C++ native code?

in the low level of dotnet library? is make simple for each function
to map to different languages?


All those languages (Ada?) compile to an intermediate language (IL). The
..Net CLR works with IL to execute code. This is how you can have a project
with VB.Net front end, C# middle tier, and C++ computation engines, if you
like.

Three sentences isn't enough to cover the subject, but you should now have
the keywords to search for to get the details.
 
All those languages (Ada?) compile to an intermediate language (IL). The
.Net CLR works with IL to execute code. This is how you can have a project
with VB.Net front end, C# middle tier, and C++ computation engines, if you
like.

so C++ project that uses .Net library will be running slower right?
since it compiled to (IL) and not native machine code? then .Net CLR
will translate the (IL) code on the fly at runtime?

Is the .Net CLR similar to Java virtual machine then? since Java is
translated to byte code (intermediate code) and Java virtural machine
is translate to machine code on the fly.
 
Carl Forsman said:
so C++ project that uses .Net library will be running slower right?
since it compiled to (IL) and not native machine code? then .Net CLR
will translate the (IL) code on the fly at runtime?

Maybe.... It depends on your task.
Is the .Net CLR similar to Java virtual machine then? since Java is
translated to byte code (intermediate code) and Java virtural machine
is translate to machine code on the fly.

Sort of similar. I don't think you can take IL compiled in VS for a PC, and
move it to a Linux box with Mono installed on it and have things work.
 
Maybe....  It depends on your task.




Sort of similar.  I don't think you can take IL compiled in VS for a PC, and
move it to a Linux box with Mono installed on it and have things work.

Actually you SHOULD be able to. The Intermediate Language for .NET is
standardized, and both implementations claim to adhere to the
standard. So it *might* work. I'm sure that there are system-
specific things you can do in your code, however, that might make it
not work.
 
Back
Top