Before it was "slang"ed, I'm pretty sure a "geek" was the freak in the carnival sideshow that bit the head off of live animals. Seriously. Anyone want to draw some parallels here? :

It's really cool - it's a full featured HTML browser that you can drop right into your apps! I think that there's an example project on CodeProject that demonstrates how to use it... if not, I'll write one up (we found some pretty cool things to do with it at work). To use it, you just drop it onto your form. Then in code you can use its Navigate() or Navigate2() functions to tell it to show some HTML page. It fires events when interesting things happen - like the user clicking on a hyperlink, or other things like that. Take a look at its properties and methods in the object browser - they're all pretty self explanatory. I'd advise creating a test project and just playing around with it for a day or two :)

I don't think that VB can use function pointers to call functions (although I'm not 100% positive). You can Declare a function and use it in VB (see docs on the Declare keyword). However your app will fail to load if wtsapi32.dll isn't on the system. A solution for this would be to encapsulate all your WTS calls in a COM object in a separate DLL. Then, if your app wants to make some WTS calls, it can create an instance of this COM object and do what needs to be done. When your app isn't on a terminal server, it won't ever create this COM object. Another solution would be to create a "stub" DLL, in C, that wrapped each function in wtsapi32 you wanted to call. Use the Declare keyword in your VB app to import each of these functions from your stub DLL. Then, when you wanted to call a certain wtsapi32 function, you'd instead call one of your stub dll's functions to do the dirty work (GetProcAddress(), call function, package return values and other info, then pass back to the calling VB function). If your project is mainly VB, I'd take solution #1. If your project is enough of a mix of C and VB that you don't mind maintaining the C stub as part of the project, go for #2.

There's a great hex editor (MFC source included) here It's not an ActiveX control, but the author is somewhat interested in turning it into one. It's completely freeware. ================== The original message was: There's one important common control missing in Windows: e Hex editor to edit binary values (files or strings). I need one for a freeware application i'm developing. If anyone has something useful, please let me know. If not, i'll have to develop it myself.
Good examples of how it could look are the editor for hex files in visual studio and the editor for hex values in regedit.

There's a great hex editor (MFC source included) here It's not an ActiveX control, but the author is somewhat interested in turning it into one. It's completely freeware. ================== The original message was: There's one important common control missing in Windows: e Hex editor to edit binary values (files or strings). I need one for a freeware application i'm developing. If anyone has something useful, please let me know. If not, i'll have to develop it myself.
Good examples of how it could look are the editor for hex files in visual studio and the editor for hex values in regedit.