We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

Include WME in VS.NET setup project

Medium Priority
286 Views
Last Modified: 2013-11-18
Hi

This is basically the situation. I have a project where I've used the Windows Media Encoder SDK (version 9). To run the program the users will of course need to have Windows Media Encoder installed. The nicest way would be to include it in my setup-project, but so far I've gotten the classic msi-error "Another installation is already ...."

All I want is to have the WME installation run from (read after) the project setup.

Can this be done? And if so, how?

// abpdk
Comment
Watch Question

Have a look at this URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;324733

It is meant for installing .NET framework together with your setup, but you can also alter it for anything else. Especially have a look at the last part:


Copied from the url:
Prepare Your Deployment Project for Use with the Setup.exe Bootstrapping Application Sample
To use the Setup.exe bootstrapping application sample with an installer that you created by using Visual Studio .NET deployment tools, you must prepare the deployment project for this scenario to work correctly. By default, a deployment project includes a Windows Installer bootstrapping application. However, the .NET Framework redistributable also includes a Windows Installer bootstrapping application. You must remove the installer bootstrapping application from your project. To do this, follow these steps: 1. In Solution Explorer, click the deployment project.
2. On the Project menu, click Properties.
3. In the Property Pages dialog box, set the Bootstrapper property to None.  
4. On the Build menu, click Build Solution.
5. Copy the Windows Installer file (.msi) to the deployment location (for example, a folder on a CD-ROM or a network share).
6. Copy the Setup.exe bootstrapping application sample and the Settings.ini file that you downloaded in the "Use Setup.exe to Distribute the .NET Framework with Your Visual Studio .NET Application" section to the deployment location, and then follow the steps in the "Customize the Settings.ini File" section

Customize the Settings.ini File
1. Open the Settings.ini file in a text editor (such as Notepad).
2. Locate the Msi=FxCopSourceSetup.msi entry, and then replace the default path with the path of your .msi file, as in the following examples: • When mySetup.msi is located on the local computer in the same folder as Setup.exe, the path is Msi=mySetup.msi.
• When the mySetup.msi is located on a network share in a folder named myProjectFolder, the path is Msi=\\myNetworkShare\myProjectFolder\mySetup.msi.
• When mySetup.msi is located in a folder named myInstallerFiles, on the same CD-ROM as Setup.exe, the path is Msi=myInstallerFiles/mySetup.msi.
 
3. Locate the FxInstallerPath=c: entry. Replace the default path with the correct path of the .NET Framework redistributable package, Dotnetfx.exe, as in the following examples: • When Dotnetfx.exe is located on the local computer in a folder named myProjectFolder, the path is FxInstallerPath=c:\myProjectFolder\.
• When Dotnetfx.exe is located on a network share in a folder named myProjectFolder, the path is FxInstallerPath=\\myNetworkShare\myProjectFolder\.
• When Dotnetfx.exe is located in a folder named myExecutables, on the same CD-ROM as Setup.exe, the path is FxInstallerPath=myExecutables/.
 
4. To verify what build number and language version of the .NET Framework is installed, specify the language in the Settings.ini file. By default, if you do not specify a language for the LanguageDirectory variable, Setup.exe verifies that the English version is installed.
5. Save the Settings.ini file.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
That's exacly what I needed...well almost anyway. This was for VS.NET 2003 and I'm running 2005 so it's a little bit different, but the main thing is that it worked! :)

Thanks!

// abpdk
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.