HeatWave 1.0.5 introduced that the MSBuild clean target builds all project references #5
-
|
In my usual environment where I have a WiX project, using the HeatWave extension, a colleague of mine had an issue that when they selected to clean our WiX project, it started building all of the WiX project's project references. In my environment, the clean action performed as expected, just cleaning the project and its project references. Unfortunately, I didn't write down what version of HeatWave I was using. My colleague is using HeatWave 1.0.5. I upgraded to HeatWave 1.0.5 for another reason, and now I have the issue as well. I have produced a small but effective reproducer Visual Studio 2022 solution, included in a zip file here. The WiX project is very simple and almost empty. It references a C# .NET 9 Console App project, that is also very simple and almost empty. When selecting to clean the WiX project, it is expected to clean both the C# Console App project, and itself. But it instead builds the C# Console App project, then cleans it directly afterwards. TestWix is the WiX project, TestApp is the C# Console App project. The "executing target" messages are very simple custom MSBuild targets in the TestApp project file, that executes when it says, in order to visualize what MSBuild targets are actually executed. As can be seen, the TestApp project executes its build target. This causes build issues when we choose the Rebuild action on our solution, as build actions collide when trying to build the same projects from multiple build threads simultaneously. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This is a known issue discussed in #2 and #3. We'll continue to follow up in #2. |
Beta Was this translation helpful? Give feedback.
This is a known issue discussed in #2 and #3. We'll continue to follow up in #2.