VB.NET uses COM interop behind the scenes, but it usually hides that complexity so you can use VB6-like syntax for performing tasks via COM automation. An example is below. Cheers, Jamal ' Compile at the command line with vbc.exe test.vb Option Explicit Imports Microsoft.VisualBasic Imports System.Windows.Forms Module Program Sub Main() Dim oShell As Object = CreateObject("WScript.Shell") Dim s As String = "%AppData%" Dim sDir As String = oShell.ExpandEnvironmentStrings(s) MessageBox.Show(sDir, "Application Data Folder") oShell = Nothing End Sub End Module -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas Sent: Wednesday, February 06, 2008 9:28 AM To: programmingblind@xxxxxxxxxxxxx Subject: Vb.net And Com Interop Hi Gang: In studies it looks like Vb.net would use Com Interop as a Interface to handle the complex parms between a Com Object and a Managed Code Project. So, would an Object like a imported DLL which has been referenced and Imported into a VB Project via the Imports Declaritive be accessed via Com Interop? This is concerning perhaps programming a WindowEyes Script from within a Vb.net project. Does this sound right so far? Rick Farmington Mich. USA __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind