I'm having another red squiggles issue with my XML parsing code.
I enable reference to System.Xml and add reference to System.Xml.Linq.dll.
This code runs fine but I cannot get rid of those red squiggles.

CODE:
Please log in to see this code.

I think it's a repercussion of the known bug:

WLP 6.9.20.7 has compiler error with LINQ methods

It's been determined that Add References isn't working correctly in 6.9.20. The developer suggested to add System.Runtime manually from the second tab while he's working on a fix. Please try and let us know.

This issue is different than addiging System.Runtime.
I have added System.Runtime immediately after upgrading to 6.9.20 as the error message mentioned about it explicitly.

Okay, it's just cosmetic. Let's wait for the new build then in which the developer has found a way to overcome red squiggles.

Issues found on 6.9.20 and they still remain on 6.9.21.

The following code have red highlight and saying errors in namespace.

CODE:
Please log in to see this code.

QUOTE:
The type or namespace name 'Xml' does not exist in the namespace 'System' (are you missing an assembly reference?)

CODE:
Please log in to see this code.

QUOTE:
The type or namespace name 'XmlDocument' could not be found (are you missing a using directive or an assembly reference?)

CODE:
Please log in to see this code.

QUOTE:
The type or namespace name 'Community' could not be found (are you missing a using directive or an assembly reference?)

CODE:
Please log in to see this code.

QUOTE:
The type or namespace name 'AlertByEmail' could not be found (are you missing a using directive or an assembly reference?)

Is it just a cosmetic issue or does it cause any problem?

If your Strategy compiles, the issue is cosmetic. See the complete list of issues fixed in 6.9.21 in this thread:
Wealth-Lab Pro® 6.9.21

If not,
1) add required references to your Strategy (System.Core, System.Xml etc.) and
2) make sure Community Components is installed (reinstall if necessary).

QUOTE:
If your Strategy compiles, the issue is cosmetic.

Yes, it compiles and works fine. So it is cosmetic issue but any plan fixing it?

Hope we get there eventually, working from high to low priority issues.