Dan
Wed Aug 17 11:45:07 CDT 2005
Yes.
Altman wrote:
> I guess I am kind of unsure what it meant by "self register." I
> thought it meant that I still had to register it myself. But this
> does mean that it will be registered when it is installed?
>
>
> "Lee Mitchell" <Leemi@online.microsoft.com> wrote in message
> news:QS7Ku6qoFHA.3672@TK2MSFTNGXA01.phx.gbl...
>> Hi Altman:
>>
>> You should be able to right click on the DLL in the InstallShield
>> interface, choose properties (I think) and then choose "self
>> register" from
>> the drop down combo box. This causes IS to self register the DLL.
>>
>> I hope this helps.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Sincerely,
>> Microsoft FoxPro Technical Support
>> Lee Mitchell
>>
>> *-- VFP9 HAS ARRIVED!! --*
>> Read about all the new features of VFP9 here:
>>
http://msdn.microsoft.com/vfoxpro/
>>
>> *--Purchase VFP 9.0 here:
>>
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
>> 69-4500-8bf2-3f06689f4ab3&type=ovr
>>
>> Keep an eye on the product lifecycle for Visual FoxPro here:
>>
http://support.microsoft.com/gp/lifeselectindex
>> - VFP5 Mainstream Support retired June 30th, 2003
>> - VFP6 Mainstream Support retired Sept. 30th, 2003
>>
>>> I built a multithreaded com server (dll) in FoxPro 9 and put it
>>> into my installshield to install. When it tries to build the
>>> installer I get this message.
>>
>>> The build was unable to extract COM information from the file <my
>>> dll file> in component <my dll file>. Please ensure that the file
>>> is self-registering and verify that the self-registration process
>>> does not fail.
>>
>>
>>> I can register it fine manually with regsvr32 but I do not want to
>>> manually register it. Is there any way around this or do I have to
>>> manually register this?
>>
>>
>>> --
>>> TIA
>>
>>> Altman
>>> VFP9