My experience of Visual Assist did not solve the underlining, as someone else has chimed in here. @reFX sounds like you have had a better experience! Is there some magic button I am missing to persuade Visual Assist to replace Intellisense? Or are we foregoing it, in turn for the Go button and class to header navigation?
Regarding .cpp inclusion, (which issue I think we should dub “inclusals” [sic. occlusals] for all the pain they are causing, and for want of a better nomenclature ) , in an ideal world I’d prefer adopt the accepted convention, as surely the whole point is cross platform compatibility, and that is bound to mean cross-compiler compatibilty sooner or later. Prejudicing VS2017 seems like a really bad idea to me. If there is a workaround, great, but as I mentioned earlier, my world is Windows dominant, so if not I may find an alternative. Haven’t ruled out DIY at this point.
Also, I found this on the nation’s favourite dev site.
For what it is worth, I hope we do find a simple workaround. Isn’t that what forks in repos are all about?