Replies: 1 comment
-
Hmm, this sounds similar to https://github.com/orgs/wixtoolset/discussions/8999#discussioncomment-12558335 (and another discussion somewhere about Clean rebuilding dependencies). There definitely seems to be an issue (or two) in HeatWave, so I'd recommend following the instructions in that other conversation to get the information in the FireGiant forum. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a solution with a number of C# projects and an installer project.
HeatWave 1.0.5.9 (the latest version) is installed in Visual Studio.
Naturally some C# project depend on each other. Say, I have project A and projects B and C both depending on A. And there are multiple dependencies between other projects.
The installer project depends on all projects which outputs it needs to include (so, on A, B, C and many others).
Before VS 17.13.3 everything was building properly. After updating VS to 17.13.3 (and later to 17.13.4, it is the same) strange things started to happen:
When building the installer project from VS it first builds all the project it depends on (correct). Then it starts building the installer project and strangely it looks like it tries to build some of the projects again. The build log I see is like this:
... building all projects, everything is ok. In particular:
15>Done building project "SomeProject.csproj".
...
36>------ Build started: Project: MyInstaller, Configuration: Release x64 ------
36>Done building project "SomeProject.csproj" // 1. The project has already been built before! Why here again? 2. And notice "36>" - it builds it as a part of the installer build.
...
A big number of build messages for C# projects all starting from 36> but nothing about building project A
...
And then I have a bunch of errors when building projects B and C because it couldn't find their dependency A (which is perfectly found when building these projects separately). All messages start from "36>", i.e. it happens as a part of the installer build. The whole build process is now noticeably longer since it builds everything twice.
Another strange thing: trying to clean the solution initiates installer project build which then again fails with the above errors when building projects B and C. So clean process fails with build errors (?)
Same solution builds OK in Azure build pipeline. So it looks like something between Visual Studio and HeatWave.
Beta Was this translation helpful? Give feedback.
All reactions