Community Forums
Page 3 of 3 FirstFirst 123
Results 11 to 12 of 12

Thread: TFS and Automated Build

  1. #11
    Join Date
    Dec 2013
    Posts
    1
    Quote Originally Posted by Christopher Painter View Post
    A simple example would look like:


    <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
    <PropertyGroup>
    <InstallShieldProductConfiguration>Default Configuration</InstallShieldProductConfiguration>
    <Configuration>Debug</Configuration>
    <InstallShieldRelease>$(Configuration)</InstallShieldRelease>
    <InstallShieldBuildDependsOn>PreBuild</InstallShieldBuildDependsOn>
    <InstallShieldProductVersion>$(MSIProductVersion)</InstallShieldProductVersion>
    </PropertyGroup>
    <ItemGroup>
    <InstallShieldProject Include="$(MSBuildProjectDirectory)\$(MSBuildProjectName).ism"/>
    <InstallShieldMergeModulePath Include="$(MSBuildProjectDirectory)\MSM"/>
    </ItemGroup>
    <ItemGroup>
    <InstallShieldPropertyOverrides Include="$(MSIProductCode)">
    <Property>ProductCode</Property>
    </InstallShieldPropertyOverrides>
    </ItemGroup>
    <Import Project="$(MSBuildExtensionsPath32)\InstallShield\2011\InstallShield.targets"/>
    <Target Name="PreBuild">
    <Exec Command="attrib -r &quot;$(MSBuildProjectDirectory)\*&quot; /S"/>
    </Target>
    </Project>
    Hi,

    Related to your post about editing isproj file.

    My problem is as follows:
    I need to build msi project with merge modules. It is working fine if I set the full path to msm file in InstallShiled Options.
    But on build server, msm is in different location. Next, I have multiple solutions. So specify all possible full paths in InstallShiled Options on build server is not good solution for me. I hope that usage of InstallShieldMergeModulePath element will helps, but is seems that this element is ignored and so, msm file is not found (event if I tested it on local machine == remove full path from InstallShiled Options, set it in InstallShieldMergeModulePath).

    The solution on build server is builded without knowing that there are specific (isproj) projects. Build platform is set to x86.

    What I want to do is to use element InstallShieldMergeModulePath with value of relative path to folder where is msm file for this concrete project, something like ".\..\msmFilder"

    Do you know why is element InstallShieldMergeModulePath ignored?




    Thanks a lot!

    Marek
    Last edited by marazt; 12-12-2013 at 05:21 AM.

  2. #12
    Join Date
    Oct 2011
    Posts
    29

    basically the newer approach with vnext builds

    Quote Originally Posted by Christopher Painter View Post
    Speechless.
    If wasn't a crazy idea, basically what you can do now with the new tfs vnext builds and release tasks

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •