bmg Forum Rss Feed

NEW POST: Prerequisites are not installed

jayaswal_raj — Sun, 20 Sep 2009 06:23:02 GMT

hi,
I am adding a custom prerequisite to my deployment project using BMG. Every thing works fine except that the installer does not detect the prerequistes prior to installing the main setup.
I am including my package.xml and product.xml as well over here. Please correct me where I making a mistake.

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="windows media 9 vcm.msi" />
</PackageFiles>
<Commands Reboot="Defer">
<Command PackageFile="windows media 9 vcm.msi">
<InstallConditions>
<BypassIf Property="VersionMsi" Compare="ValueExists" Value="N/A for ValueExists and ValueNotExists" />
<FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="Anunexpectederroroccurre" />
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success" />
<ExitCode Value="4121" Result="Fail" String="donotrequired" />
<DefaultExitCode Result="Fail" String="Anunexpectedexitcodewasr" FormatMessageFromSystem="true" />
</ExitCodes>
</Command>
</Commands>
<Strings>
<String Name="Culture">en</String>
<String Name="DisplayName">Windows Media Codec</String>
<String Name="Anunexpectederroroccurre">An unexpected error occurred. The product was unable to install.</String>
<String Name="donotrequired">donotrequired</String>
<String Name="Anunexpectedexitcodewasr">An unexpected exit code was returned from the installer. The installation failed.</String>
</Strings>
</Package>

Product.xml
<?xml version="1.0" encoding="utf-8"?>
<Product ProductCode="Windows.Media.9.VCM" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" />

NEW POST: Suppress .Net 3.51 SP1 EULA

ToddK — Wed, 29 Jul 2009 14:56:18 GMT

My users are choosing to not agree with the EULA, which then returns and error number, and more importantly, makes our application have a bad day.
Is there a way to update the .Net 3.51 SP1 bootstrap manifest package to suppress the EULA?

NEW POST: Working Directory

smiles3983 — Wed, 27 May 2009 22:09:43 GMT

I have a setup.exe file which uses a .dat file during its installation. When the bootstrapper executes my setup.exe file, it can't find the .dat file. How do I specify the working directory? I have included the .dat file in the bootstrapper and when I look in the folder, they are both there.

NEW POST: SQL Server 2008 SP1

petermcc — Wed, 20 May 2009 22:35:40 GMT

Hi Everyone,

I managed to figure out a work around which will be fine for now. I am somewhat making an assumption that it has worked without testing it completely yet.

Under my bootstrapper folder, C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\SqlExpress2008\en, I found the file package.xml, which has 2 public keys in it which were not matching the new SQL Express 2008 SP1 packages.

All I had to do was right click on the new installer packages (SQLEXPR32x86ENU.EXE, and SQLEXPRx64ENU.EXE), select properties. Go to the Digital Signatures tab, double click the digital signature. If I then click view certificate and go to the details tab. I can scroll down to 'Public Key'. If I copy and paste the key there and take out all the spaces, that is the public key I need to use.

So to summarise the public key needed in the package.xml file is the public key of the digital signature on the installation package.

A lot of people on the net give the impression that the public key is some kind of hash of the install package, so don't pay any attention to that.

NEW POST: SQL Server 2008 SP1

petermcc — Wed, 20 May 2009 05:10:43 GMT

Hi All,

We have been using Bootstrapper Manifest Generator for a while now, and it has worked great for us.

Our bootstrapper installs SQL Server 2008 Express as a prerequisite for our software (and other stuff too).

I would like to upgrade the bootstrapper to install SQL Server 2008 SP1. Is Bootstrapper Manifest Generator going to be updated to work with SQL Server 2008 SP1 soon?

I tried to update the SQL installation files in our installation package with the newer ones (SQLEXPR32x86ENU.EXE, and SQLEXPRx64ENU.EXE) but when I run the installer it says that the packages have been tampered with. I am guessing that is because the public keys are different.

I was wondering in the package.xml file, perhaps all I need to do is update the public keys, and rebuild the bootstrapper package. That would alternatively work, but I am not exactly sure how to work out what the new public keys should be.

Thanks,

Peter.

NEW POST: Not able to view the custom prerequisites in VS 2008

brettney — Tue, 19 May 2009 12:40:58 GMT

Check in your product.xml in the package folder that the Product Code attribute is set:
<Product ProductCode="Visual Fox Pro 9.0" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper">

If it's not it won't show up in the prerequisites.

e.g.

<Product ProductCode="" xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper">

NEW POST: Not able to view the custom prerequisites in VS 2008

JLO — Fri, 15 May 2009 19:30:16 GMT

I downloaded the Bootstrapper manifest generator and followed the steps properly.

The build output was successful with 0 warning and I could see the output folder on

C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages.

However it is not appearing in the prerequisites window in my visual studio IDE.

Am I missing some cases. I am using Microsoft Visual C# 2008 express edition.

Any help would be really appreciated.

Urgent it is!

Thanks!

NEW POST: BMG for VS2005 Capabilities?

ColbyRingeisen — Fri, 15 May 2009 16:43:00 GMT

Pardon the newbie question, but I know the VS2005/BMG bootstrapper can do everything I need except I don't know about the things below. Can it do all of the following:

Can the bootstrapper executable be renamed (such as "MyInstall.exe" instead of "setup.exe")?
Can the bootstrapper run with absolutely no UI by default (as in w/o the user needing to specify a specific "silent" or "unattended" command line)?
Can the product.xml/package.xml manifests be left external to the bootstrapper (not streamed into the exe as a resource)?

I've been using InstallShield for bootstrapping up to this point but the bootstrapper is basically a "black box" I have very little-to-no control over. I have two separate bootstrappers "SetupMyProduct.exe" (for first-time installs only) and "UpdateMyProduct.exe" (for updating previously installed product) that each run with a full UI and I need something to "bootstrap the bootstrappers" so there's one starting point for my customers.

NEW POST: Need exit code/installation condition if language pack installation fails

dhanvin — Thu, 14 May 2009 09:59:24 GMT

Hi,

I am using BMG tool to bootstrap german language pack along with .net framework 2.0 and windows installer 3.1 to deploy windows application.
I would like to know if there is any exit code/installation condition available in proudct.xml for german language pack so that if due to any reason installation of german language pack fails but, setup continues to install window application??

NEW POST: Need Product Manifest for Crystal Reports 10 Runtime

vivekd — Fri, 01 May 2009 05:40:23 GMT

Hi

I need Product Manifest for Crystal Reports 10 Runtime. Else if anyone is having information about the installation checks for it then please do provide it.

Thanks

NEW POST: Pass through command line arguments

nekno — Wed, 11 Mar 2009 00:57:12 GMT

DavidGuyer wrote:

Command line parameters, when passed through setup.exe, are passed to the final application installer, particularly in the .MSI/Setup case.

Thanks for your response, but I'm confused. Command line parameters are or are not passed thru setup.exe to the final application installer? That's what I'm trying to accomplish - to pass command line arguments through setup.exe down to the final installer. I thought going through the bootstrapper was the way to go.

I've created a bootstrapper that downloads and installs SQL Express, and built setup.exe with the BMG tool. When I run setup.exe, I want to pass in command line parameters for the SQL Express installer.

Currently, parameters won't make it thru setup.exe to the SQL Express installer, but I can specify parameters when creating the bootstrapper that will pass thru. The drawback is that I have to hard-code the parameters in the bootstrapper.

I also tried including the bootstrapper in a setup.exe built by a Visual Studio setup project. Same results.

How can I get command line arguments from the setup.exe command line to the SQL Express installer started by the bootstrapper?

Thanks.

I also posted my question to the ClickOnce/Setup forum: http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/6e8f843b-2f1d-43e1-8c2d-5afb1c772abf

NEW POST: BMG.exe Command Line support ??

ColoradoKid — Tue, 10 Mar 2009 17:56:17 GMT

Referenced in Help and when looking at the BMG.exe in reflector I see there is code to accept command line parameters to build projects.

However using "/?" or any of the other combinations will not return the Usage text or even error messages?
Is this a bug?
Will it be fixed soon?
I'd like to be able to build a package manifest (VSBootstrapperManifest) from MSBuild via the BMG.exe command lines... Is this even possible?

Thanks in advance.

NEW POST: x86 or x64 conditions

DavidGuyer — Mon, 09 Mar 2009 19:27:32 GMT

Gravy wrote:
Aha! Found it. My condition should has included:

<BypassIf Property="VersionNT64" Compare="ValueNotExists" Value="N/A for ValueExists and ValueNotExists" />

Regards

Graham

We usually use the ProcessorArchitecture variable... as in:

<FailIf Property="ProcessorArchitecture" Compare="ValueEqualTo" Value="IA64" String="InvalidPlatformArchitecture" />

{quote}

NEW POST: Pass through command line arguments

DavidGuyer — Mon, 09 Mar 2009 19:12:32 GMT

nekno wrote:
Is there a way, using a variable like %PassThroughArguments% in the Arguments field or some other method, to pass through command line arguments to a particular bootstrapper? For example, creating manifests for Windows Installer 4.5 and SQL 2008 Express, and then passing through command line arguments to the SQL Express installer from the setup.exe command line.

There isn't a way to do that today. Command line parameters, when passed through setup.exe, are passed to the final application installer, particularly in the .MSI/Setup case. They don't pass through to a specific bootstrapper package. You can edit the arguments in the product.xml or package.xml, but that is burned into setup.exe and can't be changed by the person doing the installing.

It's something we can see some benefits to doing and hope to do in a future release. I can't promise if or when it will be done though!

David Guyer

NEW POST: An unhandled exception ('Lauch for user') occured in BMG.exe

Elwin68 — Fri, 06 Mar 2009 11:12:31 GMT

I have installed 'Bootstrapper Manifest Generator for VS2008' on my laptop with Windows XP SP3.
A new MSBuild project is made with File - New.
On the tab Packages the options '.NET Framework 3.5 SP1' and 'Windows Installer 3.1' are selected.

After clicking on the link 'Download missing files' the dialog 'Visual Studio Just-In-Time Debugger' appeares with the following error:
An unhandled exception ('Lauch for user') occured in BMG.exe
At the end of the error message a random number is shown.

How can I solve the error and download the missing files?

Thanks in advance.

NEW POST: x86 or x64 conditions

Gravy — Thu, 05 Mar 2009 13:22:29 GMT

Aha! Found it. My condition should has included:

<BypassIf Property="VersionNT64" Compare="ValueNotExists" Value="N/A for ValueExists and ValueNotExists" />

Regards

Graham

NEW POST: x86 or x64 conditions

Gravy — Thu, 05 Mar 2009 12:49:00 GMT

Hi,

I'm trying to create a package that will install one of the SQL2008 components (Sqlncli). This comes in two different msi files, one for x86 and one for x64. I want my package to include both msi's but use a InstallCondition that determines which one to actually install.

I'm using the following condition for the x64 file:

<Command PackageFile="setupcomp64.msi">
<InstallConditions>
<BypassIf Property="64Installed" Compare="ValueGreaterThan" Value="0" />
<BypassIf Property="VersionNT64" Compare="VersionLessThanOrEqualTo" Value="0" />
</InstallConditions>
<ExitCodes>
<DefaultExitCode Result="Success" String="Anunexpectedexitcodewasr" FormatMessageFromSystem="true" />
</ExitCodes>
</Command>

But when the setup.exe is run on a x86 OS it still installs the x64 file.

Does anyone have idea's what I'm doing wrong?

Regards

Graham

NEW POST: Pass through command line arguments

nekno — Wed, 25 Feb 2009 05:21:41 GMT

Is there a way, using a variable like %PassThroughArguments% in the Arguments field or some other method, to pass through command line arguments to a particular bootstrapper? For example, creating manifests for Windows Installer 4.5 and SQL 2008 Express, and then passing through command line arguments to the SQL Express installer from the setup.exe command line.

NEW POST: Can't download it...

sk2000 — Wed, 28 Jan 2009 18:51:48 GMT

when i clicked on msi file to download, nothing happen. Just takes be back to same page. Got jscript error: 'CodePlex' undefined.

NEW POST: How does this tool work with Razzle build?

DavidGuyer — Thu, 22 Jan 2009 21:05:05 GMT

hle99 wrote:
Is this possible to use this tool in a Razzle build environment and if so, how? I know this tool works with MSBuild. Thanks.

I honestly don't know. I didn't design it to run within Razzle, but don't why it wouldn't either. Contact me directly at MS :-)