Assembly language link with VB.NET

[Chin Fui]

I am writting a CD-ROM Emulator application using assembly language and link
with the VB.NET interface. But, I am not sure whether assembly language is
linkable with VB.NET.

Another question is I am now stuck in the coding, not much idea in
implementing this application. I hope to get some hints on that...

Thank you.

Chin Fui

 

[Tom Spink]

Hi, If it is linkable, which I doubt very much it is.... I wouldn't pursue
it anyway, because VB.NET compiles to machine-indepenant bytecode. Assembly
language is machine-dependant code.

--
HTH,
-- Tom Spink, Über Geek

Woe be the day VBC.EXE says, "OrElse what?"

Please respond to the newsgroup,
so all can benefit

 

[Tom Leylan]

Tom: If you can access your CD-ROM with VB.Net why wouldn't you be able to
access a CD-ROM emulator with VB.Net? It's a device accessed through a
driver... we aren't using special VB.Net compatible audio and video drivers
are we?

Chin: I can't see why you couldn't use assembly language.

 

[Ralph]

I am writting a CD-ROM Emulator application using assembly language and link
with the VB.NET interface. But, I am not sure whether assembly language is
linkable with VB.NET.

Another question is I am now stuck in the coding, not much idea in
implementing this application. I hope to get some hints on that...

Thank you.

Chin Fui

The easiest method would be to compile your "assembly language" code
(separate lib or as embedded asm instructions in C, ...) and then create a
managed C++ assembly to provide a wrapper for the asm routines. You can then
use the new classes directly in your VB code using
System::Runtime::InteroptServices

-ralph

 

[Tom Leylan]

Ralph,

I'm obviously not the person who posted the original question but at I am at
a loss to understand now a CD-ROM emulator would be compiled into a VB.Net
application. I'm far from an expert but what would the advantage of coding
it into an app be? I only ask since nobody I know of is offering VB.Net
libraries specifically designed for hardware-based CD-ROMs...

Even if one could (and I find it hard to believe one couldn't) what would
the advantage be? They operate across all languages currently why would
anybody target .Net? It seems incredibly limiting. Not if it "had" to be
done that way but it doesn't appear to be necessary.

 

[Ralph]

Ralph,

I'm obviously not the person who posted the original question but at I am at
a loss to understand now a CD-ROM emulator would be compiled into a VB.Net
application. I'm far from an expert but what would the advantage of coding
it into an app be? I only ask since nobody I know of is offering VB.Net
libraries specifically designed for hardware-based CD-ROMs...

Even if one could (and I find it hard to believe one couldn't) what would
the advantage be? They operate across all languages currently why would
anybody target .Net? It seems incredibly limiting. Not if it "had" to be
done that way but it doesn't appear to be necessary.


language

Tom,

I must have hit the wrong reply button. Did I accidently email you directly?
I apologize.

Actually I am with you - I am not sure where such a thing would 'fit' within
an 'application', be it .NET, C runtime, etc... I just knee-jerked responded
to someone that appeared to be asking "How can I use my asm within a .NET
application"? Without a second thought as to whether such a thing would
even be necessary or practical.

I often fail to have second-thoughts. <g>

-ralph

 

[Tom Spink]

My point is that VB.NET and C# and indeed anything that compiles to MSIL is
designed to be platform independant. If I write a replica of Notepad in
VB.NET and compile it, and not use any external API, then I expect it to
work exactly the same on Linux, MacOS, FreeBSD or any other platform with a
version of the .NET framework.

If I start using Assembly language, I lose that platform independancy.

--
HTH,
-- Tom Spink, Über Geek

Woe be the day VBC.EXE says, "OrElse what?"

Please respond to the newsgroup,
so all can benefit

 

[Tom Leylan]

Not a problem Tom... you'll find this is not the case despite the
advertising. We've been there, in the past it was called Java.

Again to clarify... your CD-ROM driver will not work in Linux, MacOs,
FreeBSD and Windows. It isn't worth arguing about however.

Take care,
Another "Tom"
..

 

[Tom Spink]

Not a problem Tom... you'll find this is not the case despite the

advertising. We've been there, in the past it was called Java.

;-) It is the future... I forsee it

Again to clarify... your CD-ROM driver will not work in Linux, MacOs,
FreeBSD and Windows. It isn't worth arguing about however.

I'm not writing the driver, it's not my driver.... I've got better things to
be doing (like writing a .net framework for every possible platform)

--
HTH,
-- Tom Spink, Über Geek

Woe be the day VBC.EXE says, "OrElse what?"

Please respond to the newsgroup,
so all can benefit