Bug report: aiproj file gets a new PropertyGroup

[ivanut2012]

Hi!

I am using Advanced Installer 9.1 build 44432, integrated with Visual Studio 2010 SP1. We are using a Version Control System, and noticed that the aiproj file gets modified every time Visual Studio starts, so that everyone needs a checked out version of this file at any time. When looking at the diffs, we see that a separate PropertyGroup tag is added to the file each time. We are using two builds in one AI file, maybe that is the problem. An excerpt of the aiproj file is given below:

Code: Select all

  <PropertyGroup Condition=" '$(Configuration)' == 'All' ">
    <DebugSymbols>false</DebugSymbols>
    <OutputPath>msi\</OutputPath>
    <EnableUnmanagedDebugging>true</EnableUnmanagedDebugging>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Debug' " />
  <PropertyGroup Condition=" '$(Configuration)' == 'Release' " />
  <PropertyGroup Condition=" '$(Configuration)' == 'All' " />
  <PropertyGroup Condition=" '$(Configuration)' == 'All' " />
  <PropertyGroup Condition=" '$(Configuration)' == 'All' " />
....

One more PropertyGroup tag with configuration = "All" is added each time Visual Studio starts..

Best regards,
Ivan Uthus

[Daniel]

Hello Ivan and welcome to Advanced Installer forums,

Do you have any others versions of Advanced Installer installed on your machine? Also, can you please send us the project files to support at advancedinstaller dot com so we can investigate?

All the best,
Daniel

[ivanut2012]

Hi again!

We are not able to share our code on the Internet, sorry about that.

But, aren't you able to reproduce on your side? I basically have an aip project with two builds (Debug and Release), and an aiproj file in Visual Studio, which is source controlled. I have integrated the aiproj with my solution so the Debug configuration of the solution builds a Debug build of the installer, and the Release configuration of the solution builds a Release build of the installer. My solution is both Win32 and x64, but I am only building Debug/Release builds for x64.

Best regards,
Ivan Uthus

[Daniel]

Hello Ivan,

We are not able to share our code on the Internet, sorry about that.

There is no need to share your code. We only need the project files (aiproj, aip, etc.), we don't need your source files. You can send us your project files by email.

But, aren't you able to reproduce on your side?

We tested your scenario, but we aren't able to reproduce your behavior.

Can you please answer to my first question from my previous post? Do you have any others versions of Advanced Installer installed on your machine?

All the best,
Daniel

[ivanut2012]

Hi again!

I am sorry for the delay. I am working as a contractor, and I have now switched assignments, so I have no longer access to the code.

This was a machine with a first time install of AI 9.1.

I am suprised that you cannot reproduce the bug, it appeared immediately when we created the project and added it to source control.

Best regards,
Ivan Uthus

[Bogdan]

Hi Ivan,

Maybe the file was modified when it was added to your source control system? This sometime happens, due to a file conflict or something else.

Regards,
Bogdan

[ivanut2012]

Hi Bogdan!

It was very consistent (and easy to see in source control compare) that this occurred every time Visual Studio was started. If you create an .aiproj file with release and debug builds, and insert my snippet from the .aiproj file above, do you get the bug?

Best regards,
Ivan Uthus

[tlango]

This also happens to me. Every time I open my solution in Visual Studio, the following line is added to the *.aiproj file.

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

Specs:
Advanced Installer 9.2
Windows 7 Pro x64 SP1
Visual Studio 2010 SP1

[Bogdan]

Can you please send us the aip, aiproj and sln files to support at advancedinstaller dot com so we can try to reproduce this on our machines? No source files are required.

Regards,
Bogdan

[Bogdan]

The project files were received and we were able to reproduce the problem with them. A fix will be available ASAP.

Regards,
Bogdan