vb.net and the old API

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

in vb6 you could use api calls in vb code to do some 'under the hood stuff' and it was fun eg open notepad from vb program

whats happened with API calls now in VB.net....is it all changed or cant be done now?

thanks
 
You can still use the API in a similar way to before, However, before you
get hooked up using unmanaged code, make sure you can do it with the 35,000
or so classes the framework has to offer.

"Google is my friend!"

Regards - OHM

john andrew said:
in vb6 you could use api calls in vb code to do some 'under the hood
stuff' and it was fun eg open notepad from vb program
 
On Thu, 10 Jun 2004 03:21:01 -0700, "john andrew" <john
in vb6 you could use api calls in vb code to do some 'under the hood stuff' and it was fun eg open notepad from vb program

whats happened with API calls now in VB.net....is it all changed or cant be done now?

thanks

It is supported, and then some...

See the "DllImport" attribute, and the "MarshalAs" attribute for
starters.
(Using "PInvoke")
You can still use "Declare", but only as a stepping stone to using
"DllImport".
 
I havent got much access to VB.net yet but judging by the responses it can do API's and more so.
Is it still called API's, what term do they use in VB.net?
 
I havent got much access to VB.net yet but judging by the responses it can do API's and more so.
Is it still called API's, what term do they use in VB.net?

It seems to be called "Platform Inkove Technology", or "PInvoke" for
short.
The technique is not restricted to only calling APIs.
APIs are still called API's as far as I am concerned!
The API is what is being invoked, and the PInvoke mechanism is doing
the invoking (calling).
Hope this helps, as it has confused me!
 
Back
Top