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!
How should I deploy additional binaries?
Hot Topic
- Visual SourceSafe Internet... ?
- WPF apps slow for some reason
- Unable to add deployment project to Sourcesafe
- Error on Visual Studio Tools for Office "v3" install
- Outlook Addin beta1 would not start Visual Studio 2005 released
- Can't install WinFX because of BITS service
- questions about VSS.
- Add Custom wizard to context menu?
- 3D Animation
- Write Attribute relation to COM+ in the AssemblyInfo.cs programmatically.
Visual Studio
- CodeBehind gone?
- Has anyone already styled a scroolbar using Expression designer?
- MembershipProvider, how are faults created?
- WCF and Windows 2000
- Capture association events
- VB6 + Crystal Reports 9 without installation
- Future Local Report functionality
- ExcelSheet deployment
- Unable to find required file 'Microsoft.VisualBasic.dll' - VS2005-B2
- Visual Studio 2005 Minimum Requirements
How should I deploy additional binaries?
Paul B.
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