Gary,  I installed orca.exe and reviewed the registry table.  The VS setup
project is indeed adding the "Record" entries with the incorrect CodeBase key
hardcoded to my dev environment.  The CodeBase for the DLL in which my struct
lives looks like it's getting the right entry with a pointer to the component
that will be resolved during install time (See inprocServer32 record).

Record\{170F76A2-4005-337E-9E7E-EC0ECA7E1238}\1.0.2152.42197
CodeBase= file:///C:/US Motion/LaSH Former/LaSHCore/obj/Debug/LaSHCore.DLL

CLSID\{56306667-621D-42BD-8C5F-607563E8C4C1}\InprocServer32
CodeBase=[#_7D0F977CED2FAA4A76A946529868AD3F]

The struct in which these wierd "Record" reg entries are being created is
typed below.  Does the attribution have this impact?  Why Does the

CLR need both the COM interop reg entry and the "record" entry to run this
code.  When I call a method that does not use this struct and

view how the references are resolved I see that it uses the inProcServer32
codebase.  When I call a method that uses this struct the CLR

uses the "Record" codeBase key to resolve and throws an error because the
DLL is not installed to this directory.

   <StructLayout(LayoutKind.Sequential, CharSet:=CharSet.Unicode)> _
   Public Structure HeaderStruct
       Public FormDataHeader_ID As Integer
       Public Operator_ID As Integer
       <MarshalAs(UnmanagedType.BStr)> _
       Public ProgramName As String
       <MarshalAs(UnmanagedType.BStr)> _
       Public LMSerialNumber As String
       <MarshalAs(UnmanagedType.BStr)> _
       Public ProductSerialNumber As String
       <MarshalAs(UnmanagedType.BStr)> _
       Public WorkOrder As String
       Public DateFormInitiated As Date
       Public CreateDate As Date
   End Structure

Any ideas on where to look next?