Extremely slow exe build - Azdo Workaround

[Worle]

I have got a project which has suddenly become extremely slow to compile (it is still stuck on Initialising build after 30 minutes, normally it will compile after ~5mins)

The application build log is very slowly entries similar to below

[AB_L Store Identity Maps](39.504)(796224):
Azdo 1794541 workaround applied on: {Path to members of classes}

Currently it has added 11 entries in ~ 30 minutes. 

I can't find much online regarding this.

Does anyone have any more information on what this workaround is/what it means the root cause of my slow down is.

[Yamaeda]

circular dependencies between libraries and classes often increase build times a lot.

[Worle]

I agree, in general this is a slow build and I suspect it is circular dependencies. 

What I was experiencing yesterday was a step change in duration though. I left it running for an hour without it completing whereas normally it takes about 5 minutes to complete.

I went through my normal checklist for issues  with builds and it started working again when I fixed a broken unit test which was in a diagram disable structure, this is something which I have also discussed here because I have been burnt by this before. https://forums.ni.com/t5/LabVIEW/Exclude-code-in-diagram-disable-structure-from-application/m-p/4394... 

[Yamaeda]

---

@Worle wrote:

I agree, in general this is a slow build and I suspect it is circular dependencies. 

What I was experiencing yesterday was a step change in duration though. I left it running for an hour without it completing whereas normally it takes about 5 minutes to complete.

I went through my normal checklist for issues  with builds and it started working again when I fixed a broken unit test which was in a diagram disable structure, this is something which I have also discussed here because I have been burnt by this before. https://forums.ni.com/t5/LabVIEW/Exclude-code-in-diagram-disable-structure-from-application/m-p/4394... 

---

Right, that has happened to me too. That's a tricky one. 🙂