|
Hi, I need to distribute vfpoledb.dll along with my application, the dll needs to be placed into C:\Program Files\Common Files\System\Ole DB (create if doesn't exists) and register it using regsvr32 How can I do that? Thanks, Igor
|
| igor_22 Wednesday, June 28, 2006 6:06 PM |
I made my own bootstrapper for this:
here is the package.xml within the 'en' directory for my bootstrapper (vfpoledb.exe is also in the en directory):
<?xml version="1.0" encoding="utf-8"?> <Package Name="DisplayName" Culture="Culture" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"> <PackageFiles CopyAllPackageFiles="false"> <PackageFile Name="vfpoledb.exe" HomeSite="http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en" PublicKey="3082010A0282010100CF38F7E1A4275EF8F0CCAACEFB3ADE3B6231460546BBF5B6051AD3B3ACC29F0F4C670828C44310F53B75797F6A91F4D633C861BFFA9190007AF0791D5D6870F690B29877B5031D2F9B9D9B75892F4A01417C9E7CCB87439BF49674999E98C1CF40575816F6C0D59216E52485718F9949ED557C65C91F380023C53EAB11D6296CC69EA0705B7DD537D4677720C306CE85F84E3480A035C41C53320157EFB128BD6C01E3AD40BC80A90949DB36E337F41D49AA2AA76BD019D3CC8E9DD686467A134AD64519A553B3E2782F2E35976B4CC6E81AB0D3D1249069ABCEFC696E3E4CFB024162DC07985D7E5CA74C27316B564CE198D8E0D11D718D3D2AC07F714DFFCF0203010001" /> </PackageFiles> <Commands Reboot="Defer"> <Command PackageFile="vfpoledb.exe" Arguments=" /S /v/qb"> <ExitCodes> <ExitCode Value="0" Result="Success" /> </ExitCodes> </Command> </Commands> <Strings> <String Name="Culture">en</String> <String Name="DisplayName">MS FoxPro OLE Provider</String> </Strings> </Package>
THEN in the parent directory i have this product.xml file:
<?xml version="1.0" encoding="utf-8"?> <Product ProductCode="MS.FoxPro.OLE.Provider" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" />
I wasn't able to make it detect installed versions or do anything elegant... but it'll let you integrate the ole provider as a prerequisite for your installation. |
| algorithm0 Thursday, January 04, 2007 8:43 PM |
I think you're supposed to use this:
http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en
and run that exe. Are you using a setup project? I think you could run this as a custom action. |
| PhilDWilson Wednesday, June 28, 2006 10:35 PM |
Or, better yet, use Bootstrapper Manifest Generator to create a bootstrapper package for this .exe and use the bootstrapper (setup.exe) to run this install before you install your application. Works with either ClickOnce or Windows Installer.
If you do this, you can post your FoxPro OLE provider bootstrapper package on GotDotNet for others! :-)
|
| David Guyer MSFT Thursday, June 29, 2006 5:14 AM |
I made my own bootstrapper for this:
here is the package.xml within the 'en' directory for my bootstrapper (vfpoledb.exe is also in the en directory):
<?xml version="1.0" encoding="utf-8"?> <Package Name="DisplayName" Culture="Culture" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"> <PackageFiles CopyAllPackageFiles="false"> <PackageFile Name="vfpoledb.exe" HomeSite="http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en" PublicKey="3082010A0282010100CF38F7E1A4275EF8F0CCAACEFB3ADE3B6231460546BBF5B6051AD3B3ACC29F0F4C670828C44310F53B75797F6A91F4D633C861BFFA9190007AF0791D5D6870F690B29877B5031D2F9B9D9B75892F4A01417C9E7CCB87439BF49674999E98C1CF40575816F6C0D59216E52485718F9949ED557C65C91F380023C53EAB11D6296CC69EA0705B7DD537D4677720C306CE85F84E3480A035C41C53320157EFB128BD6C01E3AD40BC80A90949DB36E337F41D49AA2AA76BD019D3CC8E9DD686467A134AD64519A553B3E2782F2E35976B4CC6E81AB0D3D1249069ABCEFC696E3E4CFB024162DC07985D7E5CA74C27316B564CE198D8E0D11D718D3D2AC07F714DFFCF0203010001" /> </PackageFiles> <Commands Reboot="Defer"> <Command PackageFile="vfpoledb.exe" Arguments=" /S /v/qb"> <ExitCodes> <ExitCode Value="0" Result="Success" /> </ExitCodes> </Command> </Commands> <Strings> <String Name="Culture">en</String> <String Name="DisplayName">MS FoxPro OLE Provider</String> </Strings> </Package>
THEN in the parent directory i have this product.xml file:
<?xml version="1.0" encoding="utf-8"?> <Product ProductCode="MS.FoxPro.OLE.Provider" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" />
I wasn't able to make it detect installed versions or do anything elegant... but it'll let you integrate the ole provider as a prerequisite for your installation. |
| algorithm0 Thursday, January 04, 2007 8:43 PM |
I have updated the bootstrapper to include install conditions so that the install is bypassed if the FoxPro dll is already installed.
It also will look for a reboot required condition.
===PACKAGE.XML===
<? xml version="1.0" encoding="utf-8"?>
< Package Name="DisplayName" Culture="Culture" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper">
< PackageFiles CopyAllPackageFiles="false">
< PackageFile Name="vfpoledb.exe" HomeSite="http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en" PublicKey="3082010A0282010100CF38F7E1A4275EF8F0CCAACEFB3ADE3B6231460546BBF5B6051AD3B3ACC29F0F4C670828C44310F53B75797F6A91F4D633C861BFFA9190007AF0791D5D6870F690B29877B5031D2F9B9D9B75892F4A01417C9E7CCB87439BF49674999E98C1CF40575816F6C0D59216E52485718F9949ED557C65C91F380023C53EAB11D6296CC69EA0705B7DD537D4677720C306CE85F84E3480A035C41C53320157EFB128BD6C01E3AD40BC80A90949DB36E337F41D49AA2AA76BD019D3CC8E9DD686467A134AD64519A553B3E2782F2E35976B4CC6E81AB0D3D1249069ABCEFC696E3E4CFB024162DC07985D7E5CA74C27316B564CE198D8E0D11D718D3D2AC07F714DFFCF0203010001" />
</ PackageFiles>
< Commands Reboot="Defer">
< Command PackageFile="vfpoledb.exe" Arguments=" /S /v /qb">
< ExitCodes>
< ExitCode Value="0" Result="Success" />
< ExitCode Value="1641" Result="SuccessReboot"/>
< ExitCode Value="3010" Result="SuccessReboot"/>
</ ExitCodes>
< InstallConditions>
< BypassIf Property="FoxProOleDbInstalled" Compare="ValueExists" />
</ InstallConditions>
</ Command>
</ Commands>
< InstallChecks>
< RegistryFileCheck Property="FoxProOleDbInstalled" Key="HKCR\CLSID\{50BAEED9-ED25-11D2-B97B-000000000000}\InprocServer32" />
</ InstallChecks>
< Strings>
< String Name="Culture">en</String>
< String Name="DisplayName">MS FoxPro OLE Provider</String>
</ Strings>
</ Package>
===PRODUCT.XML=== included for completion
<?xml version="1.0" encoding="utf-8"?>
< Product ProductCode="MS.FoxPro.OLE.Provider" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" />
The PACKAGE.XML file goes in C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\FoxProOleDb\en
The PRODUCT.XML file goes in C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\FoxProOleDb
The VFPOLEDB.EXE file from Microsoft goes in C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\FoxProOleDb\en
Enjoy!
Curtis
|
| Curtis Gray Friday, April 20, 2007 2:30 AM |
I'm having the same issue here. This all seems to work fine, except that vfpoledb.exe does not seem to exist anymore. If you go to the download site, http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en&displaylang=en , you get VFPOLEDBSetup.msi, not vfpoledb.exe. So I tried this approach, substituting "vfpoledb.exe" with "VFPOLEDBSetup.msi" , and changing the publickey to that of VFPOLEDBSetup.msi, but It does not install the vfpoledb.dll.
Obviously, I can install VFPOLEDBSetup.msi separtely, but I would like to include it in our product's setup. I tried launching this setup as a custom action, but that does not work because you are not allowed to have more than one msi package running at the same time.
Any thoughts? |
| WRBehning Saturday, February 16, 2008 8:04 PM |
I am also having the same issue.
How did you resolve your issue?
Thanks.
|
| BharatPanchal Monday, March 24, 2008 4:37 PM |
Actually what I did was to include the vfpoledb.msm module. I found it in :C:\Program Files\Common Files\Merge Modules\vfpoledb.msm. This seemed to install and register the dll fine. However, it is not the latest version of the dll.
|
| WRBehning Tuesday, March 25, 2008 1:41 PM |