Visual Studio Development Bookmark and Share   
 index > Visual Studio Guidance Automation Toolkit > How should I deploy additional binaries?
 

How should I deploy additional binaries?

I have binaries that make up the framework for which I am providing guidance. What's the best way to deploy those binaries with my guidance package so that I have one msi per functional area that installs the guidance and the corresponding binaries?

Thanks!
dwj  Saturday, March 25, 2006 4:26 AM
It largely depends on the deployment strategy for your framework.
If you want to version the framework independently of the package, and that framework is reused across multple guidance packages, you should have a separate MSI for it, as that makes for easier corporate-wide push deployments, as well as easier patch deploys, etc. From your guidance package setup project you just specify a prerrequisite for its installation.

If you want to include the binaries with your package, you can also do that. Put your binaries in a Lib folder in the package, set its Build Action to Content and Copy to Output as Copy if newer. Then, you can simply copy them from the guidance package to a corresponding Lib folder in your end product (the developer solution) through an action (use the IConfigurationService.BasePath to locate the package installation location where you will take the binaries from). After that, you simply add a reference to the library from the necessary projects, again using another action.

HTH
kzu  Saturday, March 25, 2006 5:42 PM
It largely depends on the deployment strategy for your framework.
If you want to version the framework independently of the package, and that framework is reused across multple guidance packages, you should have a separate MSI for it, as that makes for easier corporate-wide push deployments, as well as easier patch deploys, etc. From your guidance package setup project you just specify a prerrequisite for its installation.

If you want to include the binaries with your package, you can also do that. Put your binaries in a Lib folder in the package, set its Build Action to Content and Copy to Output as Copy if newer. Then, you can simply copy them from the guidance package to a corresponding Lib folder in your end product (the developer solution) through an action (use the IConfigurationService.BasePath to locate the package installation location where you will take the binaries from). After that, you simply add a reference to the library from the necessary projects, again using another action.

HTH
kzu  Saturday, March 25, 2006 5:42 PM

You can use google to search for other answers

Custom Search

More Threads

• Where do I type in export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:...?
• How to execute value editor from custom wizard ?
• Extending Designer Toolbox
• Can't create my own action
• GAT/GAX with Visual Studio 2010 beta
• Error while using Guidance package in Ent Lib 3.0 for Strong Naming DLLs
• Recipe Framework Error when created SCSF project
• How do you enable delay signing on a web project programmatically?
• T4 generating duplicate code file with different name
• Installing Clarius SFT for July 2007 GAT CTP