First of all, I hope this is the correct forum for this question...

I'm converting a VBA project in Outlook 2003 using VS.Net 2003. I've run into several roadblocks (aside from sorting out reference issues!):

1. Windows API declaration giving compiler errors (this is code I found a long time ago. I know it works in VBA):

Public Declare Function RegQueryValueEx Lib "advapi32.dll" _
Alias "RegQueryValueExA" (ByVal hKey As Long, _
ByVal lpValueName As String, _
ByVal lpReserved As Long, _
ByVal lpType As Long, _
ByVal lpData As Any, _ ' <-- As Any not supported...
ByVal lpcbData As Long) As Long

In the same module (I can't seem to find an equivalent string creation routine for VB):

strBuf = String(lDataBufSize, " ") ' <-- String is a class type...

2. In a Windows Form code module:
'...
Dim HTML As New mshtml.HTMLDocument
HTML = Me.ctlWB.Document
HTML.images(Text).src '<--
'mshtml.IHTMLElementCollection' cannot be indexed
'because it has no default property.

Hope someone can shed some light on this. Haven't used VS much so I'm very rusty...

3. Is it possible to build a COM Add-In without having to distribute the .Net Framework? For a simple Office COM Add-In (which is essentially one DLL), this seems like overkill.