jdshkolnik
Posts: 14
Joined: Tue Mar 22, 2016 3:40 pm
Contact: Website

Multiple PropertyGroup entries for DefaultBuild

My test project .aiproj file has 4 duplicate entries like this:

<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />

I remove the duplicates, check it in, and when I open again it adds a new duplicate.
John D. Shkolnik
Senior Manager
Financial Technology
Deloitte & Touche LLP
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi John,

Indeed, this is an Advanced Installer issue which we are aware of, but you can ignore for the moment it as it should not brake the project. A fix for it will be included in a future version of Advanced Installer. Thank you for understanding.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dan
Posts: 4529
Joined: Wed Apr 24, 2013 3:51 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hello,

This was fixed in version 13.1 of Advanced Installer released on July 19th, 2016.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
gthomas
Posts: 3
Joined: Fri May 12, 2017 5:07 am

Re: Multiple PropertyGroup entries for DefaultBuild

Hi,
I'm getting this same issue now using advanced installer 14.0.1 and visual studio 2017 professional. It also had the issue with the previous version of AI, which I think was 13.8.1, but I'm not 100% sure of that version number.

Thanks
Garry
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi Garry and welcome to our forums.

Indeed, it seems that this error reappeared in the latest versions of our product. We will fix it in a future version of Advanced Installer. Thank you for bringing it to our attention.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
fstrohmaier
Posts: 1
Joined: Tue Jun 20, 2017 8:13 am

Re: Multiple PropertyGroup entries for DefaultBuild

Hi,

we've the same issue with V14.0.2.
Please fix it asap! We have problems with that because our version-constrol-system always recognise changes of the project!
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi,

This was already fixed and it will be available in the next version of Advanced Installer. We will update this thread when the new version will be released.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jdshkolnik
Posts: 14
Joined: Tue Mar 22, 2016 3:40 pm
Contact: Website

Re: Multiple PropertyGroup entries for DefaultBuild

I just updated to new version and it keeps forcing my "All" configuration to become "DefaultBuild".
John D. Shkolnik
Senior Manager
Financial Technology
Deloitte & Touche LLP
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi John,

This is the normal behavior in case of existing only one configuration, the "All" configuration is automatically turned to "DefaultBuild" in this case.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jdshkolnik
Posts: 14
Joined: Tue Mar 22, 2016 3:40 pm
Contact: Website

Re: Multiple PropertyGroup entries for DefaultBuild

Eusebiu wrote:Hi John,

This is the normal behavior in case of existing only one configuration, the "All" configuration is automatically turned to "DefaultBuild" in this case.

Best regards,
Eusebiu
Then why doesn't it rename the default configuration as well? It ends up like this:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">All</Configuration>
    <SchemaVersion>2.0</SchemaVersion>
    <ProjectGuid>f3fa2c3b-7f3b-4160-b4aa-75835a42fa8f</ProjectGuid>
    <OutputType>msi</OutputType>
    <ProjectHome>.</ProjectHome>
    <StartupFile>Blahblah-Install.aip</StartupFile>
    <SearchPath>
    </SearchPath>
    <WorkingDirectory>.</WorkingDirectory>
    <IsWindowsApplication>True</IsWindowsApplication>
    <AssemblyName>Blahblah-Install</AssemblyName>
    <Name>Blahblah-Install</Name>
    <RootNamespace>Blahblah-Install</RootNamespace>
    <SccProjectName>SAK</SccProjectName>
    <SccProvider>SAK</SccProvider>
    <SccAuxPath>SAK</SccAuxPath>
    <SccLocalPath>SAK</SccLocalPath>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
  <ItemGroup>
    <Compile Include="Blahblah-Install.aip">
      <SubType>Code</SubType>
    </Compile>
  </ItemGroup>
  <Import Project="$(MSBuildExtensionsPath32)\Caphyon\Advanced Installer\AdvInstExtTasks.Targets" />
</Project>
John D. Shkolnik
Senior Manager
Financial Technology
Deloitte & Touche LLP
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi John,
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">All</Configuration>
This block is setting the "Configuration" property of the project to "All" if no configuration is specified ('$(Configuration)' == '' "). This is not a project configuration.
<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
The above line represents the project configuration. The configuration is called "DefaultBuild" because there is a synchronization between the builds defined in the AIP file and the AIPROJ file.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jdshkolnik
Posts: 14
Joined: Tue Mar 22, 2016 3:40 pm
Contact: Website

Re: Multiple PropertyGroup entries for DefaultBuild

Eusebiu wrote:Hi John,
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">All</Configuration>
This block is setting the "Configuration" property of the project to "All" if no configuration is specified ('$(Configuration)' == '' "). This is not a project configuration.
<PropertyGroup Condition=" '$(Configuration)' == 'DefaultBuild' " />
The above line represents the project configuration. The configuration is called "DefaultBuild" because there is a synchronization between the builds defined in the AIP file and the AIPROJ file.

Best regards,
Eusebiu
I'm familiar with what each block is for. My point is that you've gotten rid of the "All" configuration yet the project is still left to default to "All" if no configuration specified.
John D. Shkolnik
Senior Manager
Financial Technology
Deloitte & Touche LLP
Dan
Posts: 4529
Joined: Wed Apr 24, 2013 3:51 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hello,

The entries duplication issue was fixed in version 14.1 of Advanced Installer released on June 30th, 2017.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
jdshkolnik
Posts: 14
Joined: Tue Mar 22, 2016 3:40 pm
Contact: Website

Re: Multiple PropertyGroup entries for DefaultBuild

Dan wrote:Hello,

The entries duplication issue was fixed in version 14.1 of Advanced Installer released on June 30th, 2017.

Best regards,
Dan
What about the discrepancy I mentioned above?
John D. Shkolnik
Senior Manager
Financial Technology
Deloitte & Touche LLP
Eusebiu
Posts: 4959
Joined: Wed Nov 14, 2012 2:04 pm

Re: Multiple PropertyGroup entries for DefaultBuild

Hi John,
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">All</Configuration>
The "All" word that appears in the above block does not refer to any configuration, it is just an internal notation that we use in case no build is specified when the project is built from command line.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”