I will test. Does IFDEF issue occur on opened file for editing? Or a background task is scanning my files after opening the project and then on unclosed define the problem raises?
We have our projects working with VS and Water with the previous stable, so the unclosed IFDEF issue would appear earlier.
Will Vika’s fix report such error in logs?
What exactly “Update File Types for …” task does?
On the background parse that Water does over all files for CC & Co.
An unclosed IFDEF would already create a compiler error. The issue was just that (in some cases) the IDE parser got stuck on them. If your project compiles clean, than this is a different issue we’d have to look at separately.
Can you elaborate?
I sent you a test case in private message.
1 Like
Build .2571 has the same problem so it’s not IFDEF.
1 Like